Universal vehicle voice command system

ABSTRACT

Methods and systems are presented for accepting inputs into a vehicle or other conveyance to control functions of the conveyance. A vehicle control system can receive gestures and other inputs. The vehicle control system can also obtain information about the user of the vehicle control system and information about the environment in which the conveyance is operating. Based on the input and the other information, the vehicle control system can modify or improve the performance or execution of user interface and functions of the conveyance. The changes make the user interfaces and/or functions user-friendly and intuitive.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims the benefits of and priority, under 35U.S.C. §119(e), to U.S. Provisional Application Ser. Nos. 61/811,981,filed on Apr. 15, 2013, entitled “Functional Specification for a NextGeneration Automobile”; 61/865,954, filed on Aug. 14, 2013, entitled“Gesture Control of Vehicle Features”; 61/870,698, filed on Aug. 27,2013, entitled “Gesture Control and User Profiles Associated withVehicle Features”; 61/891,217, filed on Oct. 15, 2013, entitled “GestureControl and User Profiles Associated with Vehicle Features”; 61/904,205,filed on Nov. 14, 2013, entitled “Gesture Control and User ProfilesAssociated with Vehicle Features”; 61/924,572, filed on Jan. 7, 2014,entitled “Gesture Control and User Profiles Associated with VehicleFeatures”; and 61/926,749, filed on Jan. 13, 2014, entitled “Method andSystem for Providing Infotainment in a Vehicle.” The entire disclosuresof the applications listed above are hereby incorporated by reference,in their entirety, for all that they teach and for all purposes.

This application is also related to U.S. patent application Ser. No.13/420,236, filed on Mar. 14, 2012, entitled, “Configurable VehicleConsole”; Ser. No. 13/420,240, filed on Mar. 14, 2012, entitled“Removable, Configurable Vehicle Console”; Ser. No. 13/462,593, filed onMay 2, 2012, entitled “Configurable Dash Display”; Ser. No. 13/462,596,filed on May 2, 2012, entitled “Configurable Heads-Up Dash Display”;Ser. No. 13/679,459, filed on Nov. 16, 2012, entitled “VehicleComprising Multi-Operating System” (Attorney Docket No. 6583-228); Ser.No. 13/679,234, filed on Nov. 16, 2012, entitled “Gesture Recognitionfor On-Board Display” (Attorney Docket No. 6583-229); Ser. No.13/679,412, filed on Nov. 16, 2012, entitled “Vehicle Application Storefor Console” (Attorney Docket No. 6583-230); Ser. No. 13/679,857, filedon Nov. 16, 2012, entitled “Sharing Applications/Media Between Car andPhone (Hydroid)” (Attorney Docket No. 6583-231); Ser. No. 13/679,878,filed on Nov. 16, 2012, entitled “In-Cloud Connection for CarMultimedia” (Attorney Docket No. 6583-232); Ser. No. 13/679,875, filedon Nov. 16, 2012, entitled “Music Streaming” (Attorney Docket No.6583-233); Ser. No. 13/679,676, filed on Nov. 16, 2012, entitled“Control of Device Features Based on Vehicle State” (Attorney Docket No.6583-234); Ser. No. 13/678,673, filed on Nov. 16, 2012, entitled“Insurance Tracking” (Attorney Docket No. 6583-235); Ser. No.13/678,691, filed on Nov. 16, 2012, entitled “Law Breaking/BehaviorSensor” (Attorney Docket No. 6583-236); Ser. No. 13/678,699, filed onNov. 16, 2012, entitled “Etiquette Suggestion” (Attorney Docket No.6583-237); Ser. No. 13/678,710, filed on Nov. 16, 2012, entitled“Parking Space Finder Based on Parking Meter Data” (Attorney Docket No.6583-238); Ser. No. 13/678,722, filed on Nov. 16, 2012, entitled“Parking Meter Expired Alert” (Attorney Docket No. 6583-239); Ser. No.13/678,726, filed on Nov. 16, 2012, entitled “Object Sensing (PedestrianAvoidance/Accident Avoidance)” (Attorney Docket No. 6583-240); Ser. No.13/678,735, filed on Nov. 16, 2012, entitled “Proximity Warning Relativeto Other Cars” (Attorney Docket No. 6583-241); Ser. No. 13/678,745,filed on Nov. 16, 2012, entitled “Street Side Sensors” (Attorney DocketNo. 6583-242); Ser. No. 13/678,753, filed on Nov. 16, 2012, entitled“Car Location” (Attorney Docket No. 6583-243); Ser. No. 13/679,441,filed on Nov. 16, 2012, entitled “Universal Bus in the Car” (AttorneyDocket No. 6583-244); Ser. No. 13/679,864, filed on Nov. 16, 2012,entitled “Mobile Hot Spot/Router/Application Share Site or Network”(Attorney Docket No. 6583-245); Ser. No. 13/679,815, filed on Nov. 16,2012, entitled “Universal Console Chassis for the Car” (Attorney DocketNo. 6583-246); Ser. No. 13/679,476, filed on Nov. 16, 2012, entitled“Vehicle Middleware” (Attorney Docket No. 6583-247); Ser. No.13/679,306, filed on Nov. 16, 2012, entitled “Method and System forVehicle Data Collection Regarding Traffic” (Attorney Docket No.6583-248); Ser. No. 13/679,369, filed on Nov. 16, 2012, entitled “Methodand System for Vehicle Data Collection” (Attorney Docket No. 6583-249);Ser. No. 13/679,680, filed on Nov. 16, 2012, entitled “CommunicationsBased on Vehicle Diagnostics and Indications” (Attorney Docket No.6583-250); Ser. No. 13/679,443, filed on Nov. 16, 2012, entitled “Methodand System for Maintaining and Reporting Vehicle Occupant Information”(Attorney Docket No. 6583-251); Ser. No. 13/678,762, filed on Nov. 16,2012, entitled “Behavioral Tracking and Vehicle Applications” (AttorneyDocket No. 6583-252); Ser. No. 13/679,292, filed Nov. 16, 2012, entitled“Branding of Electrically Propelled Vehicles Via the Generation ofSpecific Operating Output” (Attorney Docket No. 6583-258); Ser. No.13/679,400, filed Nov. 16, 2012, entitled “Vehicle Climate Control”(Attorney Docket No. 6583-313); Ser. No. 13/840,240, filed on Mar. 15,2013, entitled “Improvements to Controller Area Network Bus” (AttorneyDocket No. 6583-314); Ser. No. 13/678,773, filed on Nov. 16, 2012,entitled “Location Information Exchange Between Vehicle and Device”(Attorney Docket No. 6583-315); Ser. No. 13/679,887, filed on Nov. 16,2012, entitled “In Car Communication Between Devices” (Attorney DocketNo. 6583-316); Ser. No. 13/679,842, filed on Nov. 16, 2012, entitled“Configurable Hardware Unit for Car Systems” (Attorney Docket No.6583-317); Ser. No. 13/679,204, filed on Nov. 16, 2012, entitled“Feature Recognition for Configuring a Vehicle Console and AssociatedDevices” (Attorney Docket No. 6583-318); Ser. No. 13/679,350, filed onNov. 16, 2012, entitled “Configurable Vehicle Console” (Attorney DocketNo. 6583-412); Ser. No. 13/679,358, filed on Nov. 16, 2012, entitled“Configurable Dash Display” (Attorney Docket No. 6583-413); Ser. No.13/679,363, filed on Nov. 16, 2012, entitled “Configurable Heads-Up DashDisplay” (Attorney Docket No. 6583-414); and Ser. No. 13/679,368, filedon Nov. 16, 2012, entitled “Removable, Configurable Vehicle Console”(Attorney Docket No. 6583-415). The entire disclosures of theapplications listed above are hereby incorporated by reference, in theirentirety, for all that they teach and for all purposes.

BACKGROUND

Whether using private, commercial, or public transport, the movement ofpeople and/or cargo has become a major industry. In today'sinterconnected world, daily travel is essential to engaging in commerce.Commuting to and from work can account for a significant portion of atraveler's day. As a result, vehicle manufacturers have begun to focuson making this commute, and other journeys, more enjoyable.

Currently, vehicle manufacturers attempt to entice travelers to use aspecific conveyance based on any number of features. Most of thesefeatures focus on vehicle safety or efficiency. From the addition ofsafety-restraints, air-bags, and warning systems to more efficientengines, motors, and designs, the vehicle industry has worked to appeasethe supposed needs of the traveler. Recently, however, vehiclemanufactures have shifted their focus to user and passenger comfort as aprimary concern. Making an individual more comfortable while travelinginstills confidence and pleasure in using a given vehicle, increasing anindividual's preference for a given manufacturer and/or vehicle type.

One way to instill comfort in a vehicle is to create an environmentwithin the vehicle similar to that of an individual's home. Integratingfeatures in a vehicle that are associated with comfort found in anindividual's home can ease a traveler's transition from home to vehicle.Several manufacturers have added comfort features in vehicles such asthe following: leather seats, adaptive and/or personal climate controlsystems, music and media players, ergonomic controls, and, in somecases, Internet connectivity. However, because these manufacturers haveadded features to a conveyance, they have built comfort around a vehicleand failed to build a vehicle around comfort.

SUMMARY

There is a need for a vehicle ecosystem, which can integrate bothphysical and mental comforts, while seamlessly communicating withcurrent electronic devices to result in a totally intuitive andimmersive user experience. These and other needs are addressed by thevarious aspects, embodiments, and/or configurations of the presentdisclosure. Also, while the disclosure is presented in terms ofexemplary and optional embodiments, it should be appreciated thatindividual aspects of the disclosure can be separately claimed.

Embodiments include a method for receiving a gesture in a conveyance,comprising: a vehicle control system, including a processor, receiving agesture from a user; the vehicle control system identifying the receivedgesture; the vehicle control system sending a verification of thereceived gesture to the user; the vehicle control system determining ifa confirmation is received in response to the verification; and if theconfirmation is received, the vehicle control system controlling afunction associated with the gesture.

An aspect of the above method further comprising: if the confirmation isnot received, the vehicle control system determining if the gestureshould be completed; and if the gesture should be completed, the vehiclecontrol system controlling the function associated with the gesture.

An aspect of the above method further comprises if the gesture shouldnot be completed, the vehicle control system determining if theverification should be resent; if the verification should be resent, thevehicle control system again sending the verification; and if theverification should not be resent, receiving another gesture.

An aspect of the above method includes wherein the verification is anaudible message presented to the user.

An aspect of the above method includes wherein the confirmation is asecond gesture.

An aspect of the above method includes wherein the confirmation is anaudible confirmation.

An aspect of the above method includes wherein the verification is auser interface message presented on a screen.

An aspect of the above method includes wherein the confirmation is aselection of a user interface device on the screen.

An aspect of the above method includes wherein the verification is apreview of the function associated with the gesture.

An aspect of the above method further comprises: the vehicle controlsystem receiving a denial of the verification; and based on the denial,the vehicle control system not completing the function associated withthe gesture.

Embodiments include a conveyance comprising: a processor operable toexecute one or more modules, the modules comprising: a gesturerecognition module operable to: receive a gesture from a user; identifythe received gesture; a verification module operable to: send averification of the received gesture to the user; determine if aconfirmation is received in response to the verification; and a functioncontrol module operable to, if the confirmation is received, control afunction associated with the gesture.

An aspect of the above conveyance includes wherein the verificationmodule further operable to, if the confirmation is not received,determine if the gesture should be completed.

An aspect of the above conveyance includes wherein the verificationmodule further operable to: if the gesture should not be completed,determine if the verification should be resent; if the verificationshould be resent, re-send the verification.

An aspect of the above conveyance includes wherein the verification isone of an audible message presented to the user, a user interfacemessage presented on a screen, or a preview of the function associatedwith the gesture.

An aspect of the above conveyance includes wherein the confirmation isone of a second gesture, a selection of a user interface device on thescreen, or an audible confirmation.

Embodiments include a non-transitory computer readable medium stored ona storage medium and having instructions that when executed by aprocessor cause the processor to perform a method, the instructionscomprising: instructions to receive a gesture from a user; instructionsto identify the received gesture; instructions to send a verification ofthe received gesture to the user; instructions to determine if aconfirmation is received in response to the verification; and if theconfirmation is received, instructions to control a function associatedwith the gesture.

An aspect of the above computer readable medium further comprises, ifthe confirmation is not received, instructions to determine if thegesture should be completed.

An aspect of the above computer readable medium further comprises: ifthe gesture should not be completed, instructions to determine if theverification should be resent; if the verification should be resent,instructions to re-send the verification.

An aspect of the above computer readable medium includes wherein theverification is one of an audible message presented to the user, a userinterface message presented on a screen, or a preview of the functionassociated with the gesture.

An aspect of the above computer readable medium includes wherein theconfirmation is one of a second gesture, a selection of a user interfacedevice on the screen, or an audible confirmation.

Embodiments include a method for modifying features of a conveyance,comprising: a vehicle control system, including a processor, identifyinga user within the conveyance; the vehicle control system retrievingcharacteristics associated with a user profile, which is associated withthe identified user; the vehicle control system determining if at leastone of the characteristics impacts the function of a vehicle; and thevehicle control system, if the at least one of the characteristicsimpacts the function of a vehicle, automatically changing a functionbased on the at least one of the characteristics.

An aspect of the above method further comprises: the vehicle controlsystem determining if an override has been set; and if the override hasbeen set, the vehicle control system ignoring the change to thefunction.

An aspect of the above method includes wherein the override is providedby the user.

An aspect of the above method includes wherein the at least one of thecharacteristics is an age of the user.

An aspect of the above method includes wherein, if the age is under apredetermined benchmark, the user is prohibited for accessing a functionof the conveyance.

An aspect of the above method includes wherein the at least one of thecharacteristics is an eyesight of the user.

An aspect of the above method includes wherein, if the eyesight is undera predetermined benchmark, a user interface is modified for the user.

An aspect of the above method includes wherein the at least one of thecharacteristics is a logged hours of the user.

An aspect of the above method includes wherein, if the logged hours isunder a predetermined benchmark, a route information is changed.

An aspect of the above method includes wherein the user is a passenger.

Embodiments include a conveyance comprising: a processor operable toexecute one or more modules, the modules comprising: a useridentification module operable to: identify a user within theconveyance; retrieve characteristics associated with a user profile,which is associated with the identified user; a user customizationmodule operable to: determine if at least one of the characteristicsimpacts the function of a vehicle; and if the at least one of thecharacteristics impacts the function of a vehicle, automatically changea function based on the at least one of the characteristics.

An aspect of the above conveyance includes wherein the usercustomization module is further operable to: determine if an overridehas been set; and if the override has been set, ignore the change to thefunction.

An aspect of the above conveyance includes wherein the at least one ofthe characteristics is an age of the user, and wherein, if the age isunder a predetermined benchmark, the user is prohibited for accessing afunction of the conveyance.

An aspect of the above conveyance includes wherein the at least one ofthe characteristics is an eyesight of the user, and wherein, if theeyesight is under a predetermined benchmark, a user interface ismodified for the user.

An aspect of the above conveyance includes wherein the at least one ofthe characteristics is a logged hours of the user, and wherein, if thelogged hours is under a predetermined benchmark, a route information ischanged.

Embodiments include a non-transitory computer readable medium stored ona storage medium and having instructions that when executed by aprocessor cause the processor to perform a method, the instructionscomprising: instructions to identify a user within the conveyance;instructions to retrieve characteristics associated with a user profile,which is associated with the identified user; instructions to determineif at least one of the characteristics impacts the function of avehicle; and if the at least one of the characteristics impacts thefunction of a vehicle, instructions to automatically change a functionbased on the at least one of the characteristics.

An aspect of the above computer readable medium further comprises:instructions to determine if an override has been set; and if theoverride has been set, instructions to ignore the change to thefunction.

An aspect of the above computer readable medium includes wherein the atleast one of the characteristics is an age of the user, and wherein, ifthe age is under a predetermined benchmark, the user is prohibited foraccessing a function of the conveyance.

An aspect of the above computer readable medium includes wherein the atleast one of the characteristics is an eyesight of the user, andwherein, if the eyesight is under a predetermined benchmark, a userinterface is modified for the user.

An aspect of the above computer readable medium includes wherein the atleast one of the characteristics is a logged hours of the user, andwherein, if the logged hours is under a predetermined benchmark, a routeinformation is changed.

Embodiments include a method for controlling functions of a conveyancewith gestures, comprising: a vehicle control system, including aprocessor, receiving a gesture within the conveyance; the vehiclecontrol system determining a location of the gesture; the vehiclecontrol system determining an origin of the gesture based on thelocation of the gesture and a location of a user providing the gesture;and the vehicle control system, based on the origin of the gesture,identifying the gesture.

An aspect of the above method further comprises: determining thelocation of the user; and determining if the location of the user isdifferent from the location of the gesture.

An aspect of the above method further comprises: if the location of theuser and the location of the gesture is same, identifying the gesture asa first gesture.

An aspect of the above method further comprises: if the location of theuser and the location of the gesture is different, identifying thegesture as a second gesture.

An aspect of the above method includes wherein the location of the useris in a first zone.

An aspect of the above method includes wherein the location of thegesture is in a second zone.

An aspect of the above method includes wherein the first gesture causesa first function to be controlled.

An aspect of the above method includes wherein the second gesture causesa second function to be controlled.

An aspect of the above method includes wherein the location of the useris in a first area.

An aspect of the above method includes wherein the location of thegesture is in a second area.

Embodiments include a conveyance comprising: a processor operable toexecute one or more modules, the modules comprising: a gesturerecognition module operable to: receive a gesture within the conveyance;determine a location of the gesture; determine an origin of the gesturebased on the location of the gesture and a location of a user providingthe gesture; and based on the origin of the gesture, identify thegesture.

An aspect of the above conveyance includes wherein the gesturerecognition module is further operable to: determine the location of theuser; determine if the location of the user is different from thelocation of the gesture; if the location of the user and the location ofthe gesture is same, identify the gesture as a first gesture; and if thelocation of the user and the location of the gesture is different,identify the gesture as a second gesture.

An aspect of the above conveyance includes wherein the location of theuser is in a first zone, and wherein the location of the gesture is in asecond zone.

An aspect of the above conveyance includes wherein the first gesturecauses a first function to be controlled, and wherein the second gesturecauses a second function to be controlled.

An aspect of the above conveyance includes wherein the location of theuser is in a first area, and wherein the location of the gesture is in asecond area.

Embodiments include a non-transitory computer readable medium stored ona storage medium and having instructions that when executed by aprocessor cause the processor to perform a method, the instructionscomprising: instructions to receive a gesture within the conveyance;instructions to determine a location of the gesture; instructions todetermine an origin of the gesture based on the location of the gestureand a location of a user providing the gesture; and based on the originof the gesture, instructions to identify the gesture.

An aspect of the above computer readable medium further comprises:instructions to determine the location of the user; instructions todetermine if the location of the user is different from the location ofthe gesture; if the location of the user and the location of the gestureis same, instructions to identify the gesture as a first gesture; and ifthe location of the user and the location of the gesture is different,instructions to identify the gesture as a second gesture.

An aspect of the above computer readable medium includes wherein thelocation of the user is in a first zone, and wherein the location of thegesture is in a second zone.

An aspect of the above computer readable medium includes wherein thefirst gesture causes a first function to be controlled, and wherein thesecond gesture causes a second function to be controlled.

An aspect of the above computer readable medium includes wherein thelocation of the user is in a first area, and wherein the location of thegesture is in a second area.

Embodiments include a method for controlling functions of a conveyancebased on gesture focus, comprising: a vehicle control system, includinga processor, receiving a gesture initiation within the conveyance; thevehicle control system identifying a focus of the gesture; the vehiclecontrol system determining user characteristics for a user making thegesture; and the vehicle control system, based on the focus and the usercharacteristics, configuring a setting for the conveyance.

An aspect of the above method includes wherein the gesture is notcompleted.

An aspect of the above method includes wherein the focus is on a userinterface.

An aspect of the above method includes wherein the vehicle controlsystem determines which user interface has the focus.

An aspect of the above method includes wherein an appearance of the userinterface changes based on the focus and before the gesture iscompleted.

An aspect of the above method includes wherein the appearance change isa change to the configuration of the user interface.

An aspect of the above method includes wherein at least oneuser-selectable button is removed from the user interface.

An aspect of the above method includes wherein a size of at least oneuser-selectable button is changed.

An aspect of the above method includes wherein a position of at leastone user-selectable button is changed.

An aspect of the above method includes wherein a shape of at least oneuser-selectable button is changed.

Embodiments include a conveyance comprising: a processor operable toexecute one or more modules, the modules comprising: a gesturerecognition module operable to receive a gesture initiation within theconveyance; a focus module operable to: identify a focus of the gesture;determine user characteristics for a user making the gesture; and afunction control module operable to, based on the focus and the usercharacteristics, configure a setting for the conveyance.

An aspect of the above conveyance includes wherein the gesture is notcompleted, and wherein the focus is on a user interface.

An aspect of the above conveyance includes wherein the vehicle controlsystem determines which user interface has the focus, and wherein anappearance of the user interface changes based on the focus and beforethe gesture is completed.

An aspect of the above conveyance includes wherein the appearance changeis a change to the configuration of the user interface.

An aspect of the above conveyance includes wherein the configurationchange is one or more of: a user-selectable button is removed from theuser interface; a size of a user-selectable button is changed; aposition of a user-selectable button is changed; and a shape of auser-selectable button is changed.

Embodiments include a non-transitory computer readable medium stored ona storage medium and having instructions that when executed by aprocessor cause the processor to perform a method, the instructionscomprising: instructions to receive a gesture initiation within theconveyance; instructions to identify a focus of the gesture;instructions to determine user characteristics for a user making thegesture; and based on the focus and the user characteristics,instructions to configure a setting for the conveyance.

An aspect of the above computer readable medium includes wherein thegesture is not completed, and wherein the focus is on a user interface.

An aspect of the above computer readable medium includes wherein thevehicle control system determines which user interface has the focus,and wherein an appearance of the user interface changes based on thefocus and before the gesture is completed.

An aspect of the above computer readable medium includes wherein theappearance change is a change to the configuration of the userinterface.

An aspect of the above computer readable medium includes wherein theconfiguration change is one or more of: a user-selectable button isremoved from the user interface; a size of a user-selectable button ischanged; a position of a user-selectable button is changed; and a shapeof a user-selectable button is changed.

Embodiments include a method for controlling a user interface in aconveyance, comprising: a vehicle control system, including a processor,providing content on the user interface; the vehicle control systemdetermining if a user within the conveyance should be prohibited fromviewing the content; the vehicle control system determining a locationof the prohibited user; and the vehicle control system modifying adisplay of the content to prevent viewing by the prohibited user.

An aspect of the above method includes wherein the content is a movie.

An aspect of the above method includes wherein the prohibited user is adriver.

An aspect of the above method includes wherein the prohibited user isanother passenger.

An aspect of the above method includes wherein the other passenger isidentified as a child.

An aspect of the above method includes wherein at least a portion of theuser interface is blacked out.

An aspect of the above method includes wherein the at least a portion ofthe user interface is blacked out when the prohibited user looks at theuser interface.

An aspect of the above method includes wherein the user interface ispivoted away from the prohibited user.

An aspect of the above method further comprises: the vehicle controlsystem determining if the prohibited user should receive audioassociated with the content; and if the prohibited user should notreceive audio associated with the content, changing an audio signal toprevent listening by the prohibited user.

An aspect of the above method includes wherein a noise cancelling signalis sent to a zone associated with the prohibited user.

Embodiments include a conveyance comprising: a processor operable toexecute one or more modules, the modules comprising: a media controlleroperable to: provide content on the user interface; modify a display ofthe content to prevent viewing by a user; a user customization moduleoperable to: determine if the user within the conveyance should beprohibited from viewing the content; and determine a location of theprohibited user.

An aspect of the above conveyance includes wherein the content is amovie.

An aspect of the above conveyance includes wherein the prohibited useris one of a driver, another passenger, or a child passenger.

An aspect of the above conveyance includes wherein the display ismodified by one of at least a portion of the user interface is blackedout when the prohibited user looks at the user interface or the displayis pivoted away from the prohibited user.

An aspect of the above conveyance includes wherein the usercustomization module is further operable to: determine if the prohibiteduser should receive audio associated with the content; and if theprohibited user should not receive audio associated with the content,change an audio signal to prevent listening by the prohibited user,wherein a noise cancelling signal is sent to a zone associated with theprohibited user.

Embodiments include a non-transitory computer readable medium stored ona storage medium and having instructions that when executed by aprocessor cause the processor to perform a method, the instructionscomprising: instructions to provide content on the user interface;instructions to determine if a user within the conveyance should beprohibited from viewing the content; and instructions to determine alocation of the prohibited user; instructions to modify a display of thecontent to prevent viewing by the prohibited user.

An aspect of the above computer readable medium includes wherein thecontent is a movie.

An aspect of the above computer readable medium includes wherein theprohibited user is one of a driver, another passenger, or a childpassenger.

An aspect of the above computer readable medium includes wherein thedisplay is modified by one of at least a portion of the user interfaceis blacked out when the prohibited user looks at the user interface orthe display is pivoted away from the prohibited user.

An aspect of the above computer readable medium further comprises:instructions to determine if the prohibited user should receive audioassociated with the content; and if the prohibited user should notreceive audio associated with the content, instructions to change anaudio signal to prevent listening by the prohibited user, wherein anoise cancelling signal is sent to a zone associated with the prohibiteduser.

Embodiments include a method for controlling a function in a conveyance,comprising: a vehicle control system, including a processor, identifyinga user within a conveyance; the vehicle control system determining alocation of the user within the conveyance; the vehicle control systemretrieving a user profile for the user based on the identity and thelocation of the user, wherein the user profile includes one or moresettings associated with the user; the vehicle control system receivingan audible command from the user, wherein the audible command is one ofthe setting associated with the user; and the vehicle control systemmodifying a function of the conveyance based on the audible command.

An aspect of the above method includes wherein the location of the useris in one of two or more areas defined in the conveyance.

An aspect of the above method includes wherein a first function iscontrolled if the audible command is received in a first area.

An aspect of the above method includes wherein a second function iscontrolled if the audible command is received in a second area.

An aspect of the above method includes wherein the location of the useris in one of two or more zones defined in the conveyance.

An aspect of the above method includes wherein a third function iscontrolled if the audible command is received in a first zone.

An aspect of the above method includes wherein a fourth function iscontrolled if the audible command is received in a second zone.

An aspect of the above method includes wherein a fifth function iscontrolled if the audible command is received from a first user.

An aspect of the above method includes wherein a sixth function iscontrolled if the audible command is received in from a second user.

An aspect of the above method further comprises: the vehicle controlsystem determining if the audible command is a search function; and ifthe audible command is a search function, the vehicle control systemsearching for another audible command based on information in thereceived audible command.

Embodiments include a conveyance comprising: a processor operable toexecute one or more modules, the modules comprising: a useridentification module operable to: identify a user within a conveyance;determine a location of the user within the conveyance; retrieve a userprofile for the user based on the identity and the location of the user,wherein the user profile includes one or more settings associated withthe user; a voice control module operable to: receive an audible commandfrom the user, wherein the audible command is one of the settingassociated with the user; and modify a function of the conveyance basedon the audible command.

An aspect of the above conveyance includes wherein the location of theuser is in one of two or more areas defined in the conveyance, wherein afirst function is controlled if the audible command is received in afirst area, and wherein a second function is controlled if the audiblecommand is received in a second area.

An aspect of the above conveyance includes wherein the location of theuser is in one of two or more zones defined in the conveyance, wherein athird function is controlled if the audible command is received in afirst zone, and wherein a fourth function is controlled if the audiblecommand is received in a second zone.

An aspect of the above conveyance includes wherein a fifth function iscontrolled if the audible command is received from a first user, andwherein a sixth function is controlled if the audible command isreceived in from a second user.

An aspect of the above conveyance includes wherein the voice controlmodule is further operable to: determine if the audible command is asearch function; and if the audible command is a search function, searchfor another audible command based on information in the received audiblecommand.

Embodiments include a non-transitory computer readable medium stored ona storage medium and having instructions that when executed by aprocessor cause the processor to perform a method, the instructionscomprising: instructions to identify a user within a conveyance;instructions to determine a location of the user within the conveyance;instructions to retrieve a user profile for the user based on theidentity and the location of the user, wherein the user profile includesone or more settings associated with the user; instructions to receivean audible command from the user, wherein the audible command is one ofthe setting associated with the user; and instructions to modify afunction of the conveyance based on the audible command.

An aspect of the above computer readable medium includes wherein thelocation of the user is in one of two or more areas defined in theconveyance, wherein a first function is controlled if the audiblecommand is received in a first area, and wherein a second function iscontrolled if the audible command is received in a second area.

An aspect of the above computer readable medium includes wherein thelocation of the user is in one of two or more zones defined in theconveyance, wherein a third function is controlled if the audiblecommand is received in a first zone, and wherein a fourth function iscontrolled if the audible command is received in a second zone.

An aspect of the above computer readable medium includes wherein a fifthfunction is controlled if the audible command is received from a firstuser, and wherein a sixth function is controlled if the audible commandis received in from a second user.

An aspect of the above computer readable medium further comprises:instructions to determine if the audible command is a search function;and if the audible command is a search function, instructions to searchfor another audible command based on information in the received audiblecommand.

Embodiments include a method for controlling a function in a conveyance,comprising: a vehicle control system, including a processor, identifyinga user within a conveyance; the vehicle control system retrieving a userprofile for the user based on the identity of the user, wherein the userprofile includes one or more of a user characteristic and a userhistory; the vehicle control system determining, based on one or more ofthe user characteristic and the user history, if a change to aninteraction with the user is needed; and if a change to an interactionwith the user is needed, the vehicle control system configuring a userinterface for the user.

An aspect of the above method further comprises: the vehicle controlsystem suggesting the user interface change to the user; and the vehiclecontrol system determining if the user accepts the change.

An aspect of the above method further comprises, if the user accepts thechange, completing the configuration of the user interface.

An aspect of the above method includes wherein the user characteristicsis a user's age and at least one application commonly used by the user.

An aspect of the above method includes wherein, when the user isdriving, prohibiting access to the application on the user interface.

An aspect of the above method includes wherein the application is asocial media application and will be distracting to the user.

An aspect of the above method further comprises completing theconfiguration change regardless of whether the user accepts the change.

An aspect of the above method includes wherein the user characteristicis a user's poor eyesight and at least one application commonly used bythe user.

An aspect of the above method includes wherein the user interfacepresents an interface with the application differently for easier accessby the user.

An aspect of the above method includes wherein at least one button toanother application, not commonly used by the user, is eliminated fromthe user interface.

Embodiments include a conveyance comprising: a processor operable toexecute one or more modules, the modules comprising: a useridentification module operable to: identify a user within a conveyance;retrieve a user profile for the user based on the identity of the user,wherein the user profile includes one or more of a user characteristicand a user history; a user customization module operable to determine,based on one or more of the user characteristic and the user history, ifa change to an interaction with the user is needed; and a functioncontrol module operable to change to an interaction with the user isneeded, the vehicle control system configuring a user interface for theuser.

An aspect of the above conveyance includes wherein the function controlmodule is further operable to: suggest the user interface change to theuser; determine if the user accepts the change; and if the user acceptsthe change, complete the configuration of the user interface.

An aspect of the above conveyance includes wherein the usercharacteristics is a user's age and at least one application commonlyused by the user, wherein, when the user is driving, prohibiting accessto the application on the user interface, and wherein the application isa social media application and will be distracting to the user.

An aspect of the above conveyance includes wherein the function controlmodule is further operable to complete the configuration changeregardless of whether the user accepts the change.

An aspect of the above conveyance includes wherein the usercharacteristic is a user's poor eyesight and at least one applicationcommonly used by the user, wherein the user interface presents aninterface with the application differently for easier access by theuser, and wherein at least one button to another application, notcommonly used by the user, is eliminated from the user interface.

Embodiments include a non-transitory computer readable medium stored ona storage medium and having instructions that when executed by aprocessor cause the processor to perform a method, the instructionscomprising: instructions to identify a user within a conveyance;instructions to retrieve a user profile for the user based on theidentity of the user, wherein the user profile includes one or more of auser characteristic and a user history; instructions to determine, basedon one or more of the user characteristic and the user history, if achange to an interaction with the user is needed; and instructions tochange to an interaction with the user is needed, the vehicle controlsystem configuring a user interface for the user.

An aspect of the above computer readable medium further comprises:instructions to suggest the user interface change to the user;instructions to determine if the user accepts the change; and if theuser accepts the change, instructions to complete the configuration ofthe user interface.

An aspect of the above computer readable medium includes wherein theuser characteristics is a user's age and at least one applicationcommonly used by the user, wherein, when the user is driving,prohibiting access to the application on the user interface, and whereinthe application is a social media application and will be distracting tothe user.

An aspect of the above computer readable medium further comprisesinstructions to complete the configuration change regardless of whetherthe user accepts the change.

An aspect of the above computer readable medium includes wherein theuser characteristic is a user's poor eyesight and at least oneapplication commonly used by the user, wherein the user interfacepresents an interface with the application differently for easier accessby the user, and wherein at least one button to another application, notcommonly used by the user, is eliminated from the user interface.

The present disclosure can provide a number of advantages depending onthe particular aspect, embodiment, and/or configuration. The embodimentspresented herein provide the user with an easily configured andunderstood system for controlling the functions of the vehicle. Theinterfaces can also be changed based on the identity and characteristicsof the user both automatically and manually, which again makes thesystem more user-friendly. These and other advantages will be apparentfrom the disclosure.

The phrases “at least one,” “one or more,” and “and/or” are open-endedexpressions that are both conjunctive and disjunctive in operation. Forexample, each of the expressions “at least one of A, B and C,” “at leastone of A, B, or C,” “one or more of A, B, and C,” “one or more of A, B,or C” and “A, B, and/or C” means A alone, B alone, C alone, A and Btogether, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. Assuch, the terms “a” (or “an”), “one or more,” and “at least one” can beused interchangeably herein. It is also to be noted that the terms“comprising,” “including,” and “having” can be used interchangeably.

The term “automatic” and variations thereof, as used herein, refer toany process or operation done without material human input when theprocess or operation is performed. However, a process or operation canbe automatic, even though performance of the process or operation usesmaterial or immaterial human input, if the input is received before theperformance of the process or operation. Human input is deemed to bematerial if such input influences how the process or operation will beperformed. Human input that consents to the performance of the processor operation is not deemed to be “material.”

The term “automotive navigation system” can refer to a satellitenavigation system designed for use in vehicles. It typically uses a GPSnavigation device to acquire position data to locate the user on a roadin the unit's map database. Using the road database, the unit can givedirections to other locations along roads also in its database. Deadreckoning using distance data from sensors attached to the drivetrain, agyroscope and an accelerometer can be used for greater reliability, asGPS signal loss and/or multipath can occur due to urban canyons ortunnels.

The term “bus” and variations thereof, as used herein, can refer to asubsystem that transfers information and/or data between variouscomponents. A bus generally refers to the collection communicationhardware interface, interconnects, bus architecture, standard, and/orprotocol defining the communication scheme for a communication systemand/or communication network. A bus may also refer to a part of acommunication hardware that interfaces the communication hardware withthe interconnects that connect to other components of the correspondingcommunication network. The bus may be for a wired network, such as aphysical bus, or wireless network, such as part of an antenna orhardware that couples the communication hardware with the antenna. A busarchitecture supports a defined format in which information and/or datais arranged when sent and received through a communication network. Aprotocol may define the format and rules of communication of a busarchitecture.

The terms “communication device,” “smartphone,” and “mobile device,” andvariations thereof, as used herein, can be used interchangeably and mayinclude any type of device capable of communicating with one or more ofanother device and/or across a communications network, via acommunications protocol, and the like. Exemplary communication devicesmay include but are not limited to smartphones, handheld computers,laptops, netbooks, notebook computers, subnotebooks, tablet computers,scanners, portable gaming devices, phones, pagers, GPS modules, portablemusic players, and other Internet-enabled and/or network-connecteddevices.

A “communication modality” can refer to any protocol- or standarddefined or specific communication session or interaction, such asVoice-Over-Internet-Protocol (“VoIP), cellular communications (e.g.,IS-95, 1G, 2G, 3G, 3.5G, 4G, 4G/IMT-Advanced standards, 3GPP, WIMAX™,GSM, CDMA, CDMA2000, EDGE, 1xEVDO, iDEN, GPRS, HSPDA, TDMA, UMA, UMTS,ITU-R, and 5G), Bluetooth™, text or instant messaging (e.g., AIM, Blauk,eBuddy, Gadu-Gadu, IBM Lotus Sametime, ICQ, iMessage, IMVU, Lync, MXit,Paltalk, Skype, Tencent QQ, Windows Live Messenger™ or MSN Messenger™,Wireclub, Xfire, and Yahoo! Messenger™), email, Twitter (e.g.,tweeting), Digital Service Protocol (DSP), and the like.

The term “communication system” or “communication network” andvariations thereof, as used herein, can refer to a collection ofcommunication components capable of one or more of transmission, relay,interconnect, control, or otherwise manipulate information or data fromat least one transmitter to at least one receiver. As such, thecommunication may include a range of systems supporting point-to-pointor broadcasting of the information or data. A communication system mayrefer to the collection individual communication hardware as well as theinterconnects associated with and connecting the individualcommunication hardware. Communication hardware may refer to dedicatedcommunication hardware or may refer a processor coupled with acommunication means (i.e., an antenna) and running software capable ofusing the communication means to send and/or receive a signal within thecommunication system. Interconnect refers some type of wired or wirelesscommunication link that connects various components, such ascommunication hardware, within a communication system. A communicationnetwork may refer to a specific setup of a communication system with thecollection of individual communication hardware and interconnects havingsome definable network topography. A communication network may includewired and/or wireless network having a pre-set to an ad hoc networkstructure.

The term “computer-readable medium,” as used herein refers to anytangible storage and/or transmission medium that participates inproviding instructions to a processor for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and transmission media. Non-volatile media includes, forexample, non-volatile random access memory (NVRAM), or magnetic oroptical disks. Volatile media includes dynamic memory, such as mainmemory. Common forms of computer-readable media include, for example, afloppy disk, a flexible disk, hard disk, magnetic tape, or any othermagnetic medium, magneto-optical medium, a compact disc read only memory(CD-ROM), any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, a random access memory (RAM), aprogrammable read only memory (PROM), and erasable programmable readonly memory EPROM, a FLASH-EPROM, a solid state medium like a memorycard, any other memory chip or cartridge, a carrier wave as describedhereinafter, or any other medium from which a computer can read. Adigital file attachment to an e-mail or other self-contained informationarchive or set of archives is considered a distribution mediumequivalent to a tangible storage medium. When the computer-readablemedia is configured as a database, it is to be understood that thedatabase may be any type of database, such as relational, hierarchical,object-oriented, and/or the like. Accordingly, the disclosure isconsidered to include a tangible storage medium or distribution mediumand prior art-recognized equivalents and successor media, in which thesoftware implementations of the present disclosure are stored. It shouldbe noted that any computer readable medium that is not a signaltransmission may be considered non-transitory.

The terms dash and dashboard and variations thereof, as used herein, maybe used interchangeably and can be any panel and/or area of a vehicledisposed adjacent to an operator, user, and/or passenger. Dashboards mayinclude, but are not limited to, one or more control panel(s),instrument housing(s), head unit(s), indicator(s), gauge(s), meter(s),light(s), audio equipment, computer(s), screen(s), display(s), HUDunit(s), and graphical user interface(s).

The term “module” as used herein refers to any known or later developedhardware, software, firmware, artificial intelligence, fuzzy logic, orcombination of hardware and software that is capable of performing thefunctionality associated with that element.

The term “desktop” refers to a metaphor used to portray systems. Adesktop is generally considered a “surface” that may include pictures,called icons, widgets, folders, etc. that can activate and/or showapplications, windows, cabinets, files, folders, documents, and othergraphical items. The icons are generally selectable to initiate a taskthrough user interface interaction to allow a user to executeapplications and/or conduct other operations.

The term “display” refers to a portion of a physical screen used todisplay the output of a computer to a user.

The term “displayed image” refers to an image produced on the display. Atypical displayed image is a window or desktop. The displayed image mayoccupy all or a portion of the display.

The term “display orientation” refers to the way in which a rectangulardisplay is oriented for viewing. The two most common types of displayorientations are portrait and landscape. In landscape mode, the displayis oriented such that the width of the display is greater than theheight of the display (such as a 4:3 ratio, which is 4 units wide and 3units tall, or a 16:9 ratio, which is 16 units wide and 9 units tall).Stated differently, the longer dimension of the display is orientedsubstantially horizontal in landscape mode while the shorter dimensionof the display is oriented substantially vertical. In the portrait mode,by contrast, the display is oriented such that the width of the displayis less than the height of the display. Stated differently, the shorterdimension of the display is oriented substantially horizontal in theportrait mode while the longer dimension of the display is orientedsubstantially vertical. A multi-screen display can have one compositedisplay that encompasses all the screens. The composite display can havedifferent display characteristics based on the various orientations ofthe device.

The term “electronic address” can refer to any contactable address,including a telephone number, instant message handle, e-mail address,Uniform Resource Locator (“URL”), Global Universal Identifier (“GUID”),Universal Resource Identifier (“URI”), Address of Record (“AOR”),electronic alias in a database, etc., combinations thereof.

The term “gesture” refers to a user action that expresses an intendedidea, action, meaning, result, and/or outcome. The user action caninclude manipulating a device (e.g., opening or closing a device,changing a device orientation, moving a trackball or wheel, etc.),movement of a body part in relation to the device, movement of animplement or tool in relation to the device, audio inputs, etc. Agesture may be made on a device (such as on the screen) or with thedevice to interact with the device.

The term “gesture capture” refers to a sense or otherwise a detection ofan instance and/or type of user gesture. The gesture capture can bereceived by sensors in three-dimensional space. Further, the gesturecapture can occur in one or more areas of a screen, for example, on atouch-sensitive display or a gesture capture region. A gesture regioncan be on the display, where it may be referred to as a touch sensitivedisplay, or off the display, where it may be referred to as a gesturecapture area.

The terms “infotainment” and “infotainment system” may be usedinterchangeably and can refer to the hardware/software products, data,content, information, and/or systems, which can be built into or addedto vehicles to enhance driver and/or passenger experience. Infotainmentmay provide media and/or multimedia content. An example isinformation-based media content or programming that also includesentertainment content.

A “multi-screen application” refers to an application that is capable ofproducing one or more windows that may simultaneously occupy one or morescreens. A multi-screen application commonly can operate insingle-screen mode in which one or more windows of the application aredisplayed only on one screen or in multi-screen mode in which one ormore windows are displayed simultaneously on multiple screens.

A “single-screen application” refers to an application that is capableof producing one or more windows that may occupy only a single screen ata time.

The terms “online community,” “e-community,” or “virtual community” canmean a group of people that interact via a computer network, for social,professional, educational, and/or other purposes. The interaction canuse a variety of media formats, including wikis, blogs, chat rooms,Internet forums, instant messaging, email, and other forms of electronicmedia. Many media formats may be used in social software separatelyand/or in combination, including text-based chat rooms and forums thatuse voice, video text or avatars.

The term “satellite positioning system receiver” can refer to a wirelessreceiver or transceiver to receive and/or send location signals fromand/or to a satellite positioning system (SPS), such as the GlobalPositioning System (“GPS”) (US), GLONASS (Russia), Galileo positioningsystem (EU), Compass navigation system (China), and RegionalNavigational Satellite System (India).

The term “social network service” may include a service provider thatbuilds online communities of people, who share interests and/oractivities, or who are interested in exploring the interests and/oractivities of others. Social network services can be network-based andmay provide a variety of ways for users to interact, such as e-mail andinstant messaging services.

The term “social network” can refer to a network-based social network.

The term “screen,” “touch screen,” “touchscreen,” or “touch-sensitivedisplay” refers to a physical structure that enables the user tointeract with the computer by touching areas on the screen and providesinformation to a user through a display. The touch screen may sense usercontact in a number of different ways, such as by a change in anelectrical parameter (e.g., resistance or capacitance), acoustic wavevariations, infrared radiation proximity detection, light variationdetection, and the like. In a resistive touch screen, for example,normally separated conductive and resistive metallic layers in thescreen pass an electrical current. When a user touches the screen, thetwo layers make contact in the contacted location, whereby a change inelectrical field is noted and the coordinates of the contacted locationcalculated. In a capacitive touch screen, a capacitive layer storeselectrical charge, which is discharged to the user upon contact with thetouch screen, causing a decrease in the charge of the capacitive layer.The decrease is measured, and the contacted location coordinatesdetermined. In a surface acoustic wave touch screen, an acoustic wave istransmitted through the screen, and the acoustic wave is disturbed byuser contact. A receiving transducer detects the user contact instanceand determines the contacted location coordinates.

The term “window” refers to a, typically rectangular, displayed image onat least part of a display that contains or provides content differentfrom the rest of the screen. The window may obscure the desktop. Thedimensions and orientation of the window may be configurable either byanother module or by a user. When the window is expanded, the window canoccupy substantially all of the display space on a screen or screens.

The terms “determine,” “calculate,” and “compute,” and variationsthereof, as used herein, are used interchangeably and include any typeof methodology, process, mathematical operation, or technique.

It shall be understood that the term “means,” as used herein, shall begiven its broadest possible interpretation in accordance with 35 U.S.C.,Section 112, Paragraph 6 or other applicable law. Accordingly, a claimincorporating the term “means” shall cover all structures, materials, oracts set forth herein, and all of the equivalents thereof. Further, thestructures, materials or acts and the equivalents thereof shall includeall those described in the summary of the invention, brief descriptionof the drawings, detailed description, abstract, and claims themselves.

The terms “vehicle,” “car,” “automobile,” and variations thereof may beused interchangeably herein and can refer to a device or structure fortransporting animate and/or inanimate or tangible objects (e.g., personsand/or things), such as a self-propelled conveyance. A vehicle as usedherein can include any conveyance or model of a conveyance, where theconveyance was originally designed for the purpose of moving one or moretangible objects, such as people, animals, cargo, and the like. The term“vehicle” does not require that a conveyance moves or is capable ofmovement. Typical vehicles may include but are in no way limited tocars, trucks, motorcycles, busses, automobiles, trains, railedconveyances, boats, ships, marine conveyances, submarine conveyances,airplanes, space craft, flying machines, human-powered conveyances, andthe like.

The term “profile,” as used herein, can refer to any data structure,data store, and/or database that includes one or more items ofinformation associated with a vehicle, a vehicle system, a device (e.g.,a mobile device, laptop, mobile phone, etc.), or a person.

The term “in communication with,” as used herein, refers to anycoupling, connection, or interaction using electrical signals toexchange information or data, using any system, hardware, software,protocol, or format, regardless of whether the exchange occurswirelessly or over a wired connection.

The preceding is a simplified summary of the disclosure to provide anunderstanding of some aspects of the disclosure. This summary is neitheran extensive nor exhaustive overview of the disclosure and its variousaspects, embodiments, and/or configurations. It is intended neither toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure but to present selected concepts of thedisclosure in a simplified form as an introduction to the more detaileddescription presented below. As will be appreciated, other aspects,embodiments, and/or configurations of the disclosure are possibleutilizing, alone or in combination, one or more of the features setforth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an embodiment of a vehicle operating environment;

FIG. 2 is a block diagram of an embodiment of a vehicle system;

FIG. 3 is a block diagram of an embodiment of a vehicle control systemenvironment;

FIG. 4 is a block diagram of an embodiment of a vehicle communicationssubsystem;

FIG. 5A is a first block diagram of an embodiment of a vehicle interiorenvironment separated into areas and/or zones;

FIG. 5B is a second block diagram of an embodiment of a vehicle interiorenvironment separated into areas and/or zones;

FIG. 5C is a third block diagram of an embodiment of a vehicle interiorenvironment separated into areas and/or zones;

FIG. 6A depicts an embodiment of a sensor configuration for a vehicle;

FIG. 6B depicts an embodiment of a sensor configuration for a zone of avehicle;

FIG. 7A is a block diagram of an embodiment of interior sensors for avehicle;

FIG. 7B is a block diagram of an embodiment of exterior sensors for avehicle;

FIG. 8A is a block diagram of an embodiment of a media subsystem for avehicle;

FIG. 8B is a block diagram of an embodiment of a user and deviceinteraction subsystem for a vehicle;

FIG. 8C is a block diagram of an embodiment of a Navigation subsystemfor a vehicle;

FIG. 9 is a block diagram of an embodiment of a communications subsystemfor a vehicle;

FIG. 10 is a block diagram of an embodiment of a software architecturefor the vehicle control system;

FIG. 11A is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11B is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11C is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11D is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11E is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11F is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11G is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11H is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11I is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11J is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 11K is a graphical representation of an embodiment of a gesturethat a user may perform to provide input to a vehicle control system;

FIG. 12A is a diagram of an embodiment of a data structure for storinginformation about a user of a vehicle;

FIG. 12B is a diagram of an embodiment of a data structure for storinginformation about a device associated with or in a vehicle;

FIG. 12C is a diagram of an embodiment of a data structure for storinginformation about a system of a vehicle;

FIG. 12D is a diagram of an embodiment of a data structure for storinginformation about a vehicle;

FIG. 13 is a flow or process diagram of a method for storing one or moresettings associated with a user;

FIG. 14 is a flow or process diagram of a method for establishing one ormore settings associated with a user;

FIG. 15 is a flow or process diagram of a method for storing one or moresettings associated with a user;

FIG. 16 is a flow or process diagram of a method for storing one or moregestures associated with a user;

FIG. 17 is a flow or process diagram of a method for reacting to agesture performed by a user;

FIG. 18 is a flow or process diagram of a method for storing health dataassociated with a user;

FIG. 19 is a flow or process diagram of a method for reacting to agesture performed by a user;

FIG. 20 is a block diagram of an embodiment of a gesture control module;

FIG. 21 is a block diagram of an embodiment of a vehicle control module;

FIG. 22 is a block diagram of an embodiment of a vehicle systems;

FIG. 23A is a diagram of an embodiment of a data structure for storingprofile information;

FIG. 23B is a diagram of an embodiment of a data structure for storinggesture information;

FIG. 24A is a graphical representation of an embodiment of a userinterface for the vehicle control system;

FIG. 24B is a graphical representation of another embodiment of a userinterface for the vehicle control system;

FIG. 25 is a flow or process diagram of a method for verifying areceived gesture;

FIG. 26 is a flow or process diagram of a method for change vehiclefunctions based on user characteristic(s);

FIG. 27 is a flow or process diagram of a method for receiving a gesturein at a different point of origin;

FIG. 28 is a flow or process diagram of a method for changing a vehiclesetting based on a gesture focus;

FIG. 29 is a flow or process diagram of a method for changing thefunction of a screen to prevent viewing by a user;

FIG. 30 is a flow or process diagram of a method for receiving a voicecommand;

FIG. 31 is a flow or process diagram of a method for changing a systeminteraction based on user characteristics.

In the appended Figs., similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a letter thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference letter or label.

DETAILED DESCRIPTION

Presented herein are embodiments of systems, devices, processes, datastructures, user interfaces, etc. The embodiments may relate to anautomobile and/or an automobile environment. The automobile environmentcan include systems associated with the automobile and devices or othersystems in communication with the automobile and/or automobile systems.Furthermore, the systems can relate to communications systems and/ordevices and may be capable of communicating with other devices and/or toan individual or group of individuals. Further, the systems can receiveuser input in unique ways. The overall design and functionality of thesystems provide for an enhanced user experience making the automobilemore useful and more efficient. As described herein, the automobilesystems may be electrical, mechanical, electro-mechanical,software-based, and/or combinations thereof.

A vehicle environment 100 that may contain a vehicle ecosystem is shownin FIG. 1. The vehicle environment 100 can contain areas associated witha vehicle or conveyance 104. The vehicle 104 is shown as a car but canbe any type of conveyance. The environment 100 can include at leastthree zones. A first zone 108 may be inside a vehicle 104. The zone 108includes any interior space, trunk space, engine compartment, or otherassociated space within or associated with the vehicle 104. The interiorzone 108 can be defined by one or more techniques, for example,geo-fencing.

A second zone 112 may be delineated by line 120. The zone 112 is createdby a range of one or more sensors associated with the vehicle 104. Thus,the area 112 is exemplary of the range of those sensors and what can bedetected by those sensors associated with the vehicle 104. Althoughsensor range is shown as a fixed and continuous oval, the sensor rangemay be dynamic and/or discontinuous. For example, a ranging sensor(e.g., radar, lidar, ladar, etc.) may provide a variable range dependingon output power, signal characteristics, or environmental conditions(e.g., rain, fog, clear, etc.). The rest of the environment includes allspace beyond the range of the sensors and is represented by space 116.Thus, the environment 100 may have an area 116 that includes all areasbeyond the sensor range 112. The area 116 may include locations oftravel that the vehicle 104 may proceed to in the future.

An embodiment of a vehicle system 200 is shown in FIG. 2. The vehiclesystem 200 may comprise hardware and/or software that conduct variousoperations for or with the vehicle 104. The operations can include, butare not limited to, providing information to the user 216, receivinginput from the user 216, and controlling the functions or operation ofthe vehicle 104, etc. The vehicle system 200 can include a vehiclecontrol system 204. The vehicle control system 204 can be any type ofcomputing system operable to conduct the operations as described herein.An example of a vehicle control system may be as described inconjunction with FIG. 3.

The vehicle control system 204 may interact with a memory or storagesystem 208 that stores system data. System data 208 may be any type ofdata needed for the vehicle control system 204 to control effectivelythe vehicle 104. The system data 208 can represent any type of databaseor other storage system. Thus, the system data 208 can be a flat filedata system, an object-oriented data system, or some other data systemthat may interface with the vehicle control system 204.

The vehicle control system 204 may communicate with a device or userinterface 212, 248. The user interface 212, 248 may be operable toreceive user input either through touch input, on one or more userinterface buttons, via voice command, via one or more image sensors, orthrough a graphical user interface that may include a gesture captureregion, as described in conjunction with the other Figs. providedherein. Further, the symbol 212, 248 can represent a device that islocated or associated with the vehicle 104. The device 212, 248 can be amobile device, including, but not limited to, a mobile telephone, amobile computer, or other type of computing system or device that iseither permanently located in or temporarily associated with, but notnecessarily connected to, the vehicle 104. Thus, the vehicle controlsystem 204 can interface with the device 212, 248 and leverage thedevice's computing capability to provide one or more of the features orfunctions as described herein.

The device or user interface 212, 248 can receive input or provideinformation to a user 216. The user 216 may thus interact with thevehicle control system 204 through the interface or device 212, 248.Further, the device 212, 248 may include or have access to device data220 and/or profile data 252. The device data 220 can be any type of datathat is used in conjunction with the device 212, 248 including, but notlimited to, multimedia data, preferences data, device identificationinformation, or other types of data. The profile data 252 can be anytype of data associated with at least one user 216 including, but in noway limited to, bioinformatics, medical information, driving history,personal information (e.g., home physical address, business physicaladdress, contact addresses, likes, dislikes, hobbies, size, weight,occupation, business contacts—including physical and/or electronicaddresses, personal contacts—including physical and/or electronicaddresses, family members, and personal information related thereto,etc.), other user characteristics, advertising information, usersettings and feature preferences, travel information, associated vehiclepreferences, communication preferences, historical information (e.g.,including historical, current, and/or future travel destinations),Internet browsing history, or other types of data. In any event, thedata may be stored as device data 220 and/or profile data 252 in astorage system similar to that described in conjunction with FIGS. 12Athrough 12D.

As an example, the profile data 252 may include one or more userprofiles. User profiles may be generated based on data gathered from oneor more of vehicle preferences (e.g., seat settings, HVAC settings, dashconfigurations, and the like), recorded settings, geographic locationinformation (e.g., provided by a satellite positioning system (e.g.,GPS), Wi-Fi hotspot, cell tower data, etc.), mobile device information(such as mobile device electronic addresses, Internet browsing historyand content, application store selections, user settings and enabled anddisabled features, and the like), private information (such as userinformation from a social network, user presence information, userbusiness account, and the like), secure data, biometric information,audio information from on board microphones, video information from onboard cameras, Internet browsing history and browsed content using an onboard computer and/or the local area network enabled by the vehicle 104,geographic location information (e.g., a vendor storefront, roadwayname, city name, etc.), and the like.

The profile data 252 may include one or more user accounts. Useraccounts may include access and permissions to one or more settingsand/or feature preferences associated with the vehicle 104,communications, infotainment, content, etc. In one example, a useraccount may allow access to certain settings for a particular user,while another user account may deny access to the settings for anotheruser, and vice versa. The access controlled by the user account may bebased on at least one of a user account priority, role, permission, age,family status, a group priority (e.g., the user account priority of oneor more users, etc.), a group age (e.g., the average age of users in thegroup, a minimum age of the users in the group, a maximum age of theusers in the group, and/or combinations thereof, etc.).

For example, a user 216 may be allowed to purchase applications (e.g.,software, etc.) for the vehicle 104 and/or a device associated with thevehicle 104 based on information associated with the user account. Thisuser account information may include a preferred payment method,permissions, and/or other account information. As provided herein, theuser account information may be part of the user profile and/or otherdata stored in the profile data 252.

As another example, an adult user (e.g., a user with an age of 18 yearsold and/or over, etc.) may be located in an area of a vehicle 104, suchas a rear passenger area. Continuing this example a child user (e.g., auser with an age of 17 years old and/or less, etc.) may be located inthe same, or close, area. In this example, the user account informationin the profile data 252 associated with both the adult user and thechild user may be used by the vehicle 104 in determining whether contentis appropriate for the area given the age of the child user. Forinstance, a graphic movie containing violence (e.g., a movie associatedwith a mature rating, such as a Motion Picture Association of America(MPAA) rating of “R,” “NC-17,” etc.) may be suitable to present to adisplay device associated with the adult user but may not be acceptableto present to the display device if a 12-year old child user may seeand/or hear the content of the movie.

The vehicle control system 204 may also communicate with or through acommunication network 224. The communication network 224 can representany type of wireless and/or wired communication system that may beincluded within the vehicle 104 or operable to communicate outside thevehicle 104. Thus, the communication network 224 can include a localarea communication capability and a wide area communication capability.For example, the communication network 224 can include a Bluetooth®wireless system, an 802.11x (e.g., 802.11G/802.11N/802.11AC, or thelike, wireless system), a CAN bus, an Ethernet network within thevehicle 104, or other types of communication networks that may functionwith or be associated with the vehicle 104. Further, the communicationnetwork 224 can also include wide area communication capabilities,including one or more of, but not limited to, a cellular communicationcapability, satellite telephone communication capability, a wirelesswide area network communication capability, or other types ofcommunication capabilities that allow for the vehicle control system 204to communicate outside the vehicle 104.

The vehicle control system 204 may communicate through the communicationnetwork 224 to a server 228 that may be located in a facility that isnot within physical proximity to the vehicle 104. Thus, the server 228may represent a cloud computing system or cloud storage that allows thevehicle control system 204 to either gain access to further computingcapabilities or to storage at a location outside of the vehicle 104. Theserver 228 can include a computer processor and memory and be similar toany computing system as understood to one skilled in the art.

Further, the server 228 may be associated with stored data 232. Thestored data 232 may be stored in any system or by any method, asdescribed in conjunction with system data 208, device data 220, and/orprofile data 252. The stored data 232 can include information that maybe associated with one or more users 216 or associated with one or morevehicles 104. The stored data 232, being stored in a cloud or in adistant facility, may be exchanged among vehicles 104 or may be used bya user 216 in different locations or with different vehicles 104.Additionally or alternatively, the server may be associated with profiledata 252 as provided herein. It is anticipated that the profile data 252may be accessed across the communication network 224 by one or morecomponents of the system 200. Similar to the stored data 232, theprofile data 252, being stored in a cloud or in a distant facility, maybe exchanged among vehicles 104 or may be used by a user 216 indifferent locations or with different vehicles 104.

The vehicle control system 204 may also communicate with one or moresensors 236, 242, which are either associated with the vehicle 104 orcommunicate with the vehicle 104. Vehicle sensors 242 may include one ormore sensors for providing information to the vehicle control system 204that determine or provide information about the environment 100 in whichthe vehicle 104 is operating. Embodiments of these sensors may be asdescribed in conjunction with FIGS. 6A-7B. Non-vehicle sensor 236 can beany type of sensor that is not currently associated with the vehicle104. For example, non-vehicle sensor 236 can be sensors in a trafficsystem operated by a third party that provides data to the vehiclecontrol system 204. Further, the non-vehicle sensor(s) 236 can be othertypes of sensors which provide information about the distant environment116 or other information about the vehicle 104 or the environment 100.These non-vehicle sensors 236 may be operated by third parties butprovide information to the vehicle control system 204. Examples ofinformation provided by the sensors 236 and that may be used by thevehicle control system 204 may include weather tracking data, trafficdata, user health tracking data, vehicle maintenance data, or othertypes of data, which may provide environmental or other data to thevehicle control system 204. The vehicle control system 204 may alsoperform signal processing of signals received from one or more sensors236, 242. Such signal processing may include estimation of a measuredparameter from a single sensor, such as multiple measurements of a rangestate parameter from the vehicle 104 to an obstacle, and/or theestimation, blending, or fusion of a measured state parameter frommultiple sensors such as multiple radar sensors or a combination of aladar/lidar range sensor and a radar sensor. Signal processing of suchsensor signal measurements may comprise stochastic signal processing,adaptive signal processing, and/or other signal processing techniquesknown to those skilled in the art.

The various sensors 236, 242 may include one or more sensor memory 244.Embodiments of the sensor memory 244 may be configured to store datacollected by the sensors 236, 242. For example, a temperature sensor maycollect temperature data associated with a vehicle 104, user 216, and/orenvironment, over time. The temperature data may be collectedincrementally, in response to a condition, or at specific time periods.In this example, as the temperature data is collected, it may be storedin the sensor memory 244. In some cases, the data may be stored alongwith an identification of the sensor and a collection time associatedwith the data. Among other things, this stored data may include multipledata points and may be used to track changes in sensor measurements overtime. As can be appreciated, the sensor memory 244 can represent anytype of database or other storage system.

The diagnostic communications module 256 may be configured to receiveand transmit diagnostic signals and information associated with thevehicle 104. Examples of diagnostics signals and information mayinclude, but is in no way limited to, vehicle system warnings, sensordata, vehicle component status, service information, component health,maintenance alerts, recall notifications, predictive analysis, and thelike. Embodiments of the diagnostic communications module 256 may handlewarning/error signals in a predetermined manner. The signals, forinstance, can be presented to one or more of a third party, occupant,vehicle control system 204, and a service provider (e.g., manufacturer,repair facility, etc.).

Optionally, the diagnostic communications module 256 may be utilized bya third party (i.e., a party other than the user 216, etc.) incommunicating vehicle diagnostic information. For instance, amanufacturer may send a signal to a vehicle 104 to determine a statusassociated with one or more components associated with the vehicle 104.In response to receiving the signal, the diagnostic communicationsmodule 256 may communicate with the vehicle control system 204 toinitiate a diagnostic status check. Once the diagnostic status check isperformed, the information may be sent via the diagnostic communicationsmodule 256 to the manufacturer. This example may be especially useful indetermining whether a component recall should be issued based on thestatus check responses returned from a certain number of vehicles.

Wired/wireless transceiver/communications ports 260 may be included. Thewired/wireless transceiver/communications ports 260 may be included tosupport communications over wired networks or links, for example withother communication devices, server devices, and/or peripheral devices.Examples of wired/wireless transceiver/communications ports 260 includeEthernet ports, Universal Serial Bus (USB) ports, Institute ofElectrical and Electronics Engineers (IEEE) 1594, or other interfaceports.

An embodiment of a vehicle control environment 300 including a vehiclecontrol system 204 may be as shown in FIG. 3. Beyond the vehicle controlsystem 204, the vehicle control environment 300 can include one or moreof, but is not limited to, a power source and/or power control module316, a data storage module 320, user interface(s)/input interface(s)324, vehicle subsystems 328, user interaction subsystems 332, GlobalPositioning System (GPS)/Navigation subsystems 336, sensor(s) and/orsensor subsystems 340, communication subsystems 344, media subsystems348, and/or device interaction subsystems 352. The subsystems, modules,components, etc. 316-352 may include hardware, software, firmware,computer readable media, displays, input devices, output devices, etc.or combinations thereof. The system, subsystems, modules, components,etc. 204, 316-352 may communicate over a network or bus 356. Thiscommunication bus 356 may be bidirectional and perform datacommunications using any known or future-developed standard or protocol.An example of the communication bus 356 may be as described inconjunction with FIG. 4.

The vehicle control system 204 can include a processor 304, memory 308,and/or an input/output (I/O) module 312. Thus, the vehicle controlsystem 204 may be a computer system, which can comprise hardwareelements that may be electrically coupled. The hardware elements mayinclude one or more central processing units (CPUs) 304; one or morecomponents of the I/O module 312 including input devices (e.g., a mouse,a keyboard, etc.) and/or one or more output devices (e.g., a displaydevice, a printer, etc.).

The processor 304 may comprise a general purpose programmable processoror controller for executing application programming or instructions. Theprocessor 304 may, optionally, include multiple processor cores, and/orimplement multiple virtual processors. Additionally or alternatively,the processor 304 may include multiple physical processors. As aparticular example, the processor 304 may comprise a speciallyconfigured application specific integrated circuit (ASIC) or otherintegrated circuit, a digital signal processor, a controller, ahardwired electronic or logic circuit, a programmable logic device orgate array, a special purpose computer, or the like. The processor 304generally functions to run programming code or instructions implementingvarious functions of the vehicle control system 204.

The input/output module 312 and associated ports may be included tosupport communications over wired or wireless networks or links, forexample with other communication devices, server devices, and/orperipheral devices. Examples of an input/output module 312 include anEthernet port, a Universal Serial Bus (USB) port, Institute ofElectrical and Electronics Engineers (IEEE) 1594, or other interface.

The vehicle control system 204 may also include one or more storagedevices 308. By way of example, storage devices 308 may be disk drives,optical storage devices, solid-state storage devices such as a randomaccess memory (“RAM”) and/or a read-only memory (“ROM”), which can beprogrammable, flash-updateable and/or the like. The vehicle controlsystem 204 may additionally include a computer-readable storage mediareader; a communications system (e.g., a modem, a network card (wirelessor wired), an infra-red communication device, etc.); and working memory308, which may include RAM and ROM devices as described above. Thevehicle control system 204 may also include a processing accelerationunit, which can include a digital signal processor (DSP), aspecial-purpose processor, and/or the like.

The computer-readable storage media reader can further be connected to acomputer-readable storage medium, together (and, optionally, incombination with storage device(s)) comprehensively representing remote,local, fixed, and/or removable storage devices plus storage media fortemporarily and/or more permanently containing computer-readableinformation. The communications system may permit data to be exchangedwith an external or internal network and/or any other computer or devicedescribed herein. Moreover, as disclosed herein, the term “storagemedium” may represent one or more devices for storing data, includingread only memory (ROM), random access memory (RAM), magnetic RAM, corememory, magnetic disk storage mediums, optical storage mediums, flashmemory devices, and/or other machine readable mediums for storinginformation.

The vehicle control system 204 may also comprise software elementsincluding an operating system and/or other code, as described inconjunction with FIG. 10. It should be appreciated that alternates tothe vehicle control system 204 may have numerous variations from thatdescribed herein. For example, customized hardware might also be usedand/or particular elements might be implemented in hardware, software(including portable software, such as applets), or both. Further,connection to other computing devices such as network input/outputdevices may be employed.

The power source and/or power control module 316 can include any type ofpower source, including, but not limited to, batteries, alternatingcurrent sources (from connections to a building power system or powerline), solar cell arrays, etc. One or more components or modules mayalso be included to control the power source or change thecharacteristics of the provided power signal. Such modules can includeone or more of, but is not limited to, power regulators, power filters,alternating current (AC) to direct current (DC) converters, DC to ACconverters, receptacles, wiring, other converters, etc. The power sourceand/or power control module 316 functions to provide the vehicle controlsystem 204 and any other system with power.

The data storage 320 can include any module for storing, retrieving,and/or managing data in one or more data stores and/or databases. Thedatabase or data stores may reside on a storage medium local to (and/orresident in) the vehicle control system 204 or in the vehicle 104.Alternatively, some of the data storage capability may be remote fromthe vehicle control system 204 or automobile, and in communication(e.g., via a network) to the vehicle control system 204. The database ordata stores may reside in a storage-area network (“SAN”) familiar tothose skilled in the art. Similarly, any necessary files for performingthe functions attributed to the vehicle control system 204 may be storedlocally on the respective vehicle control system 204 and/or remotely, asappropriate. The databases or data stores may be a relational database,and the data storage module 320 may be adapted to store, update, andretrieve data in response to specifically-formatted commands. The datastorage module 320 may also perform data management functions for anyflat file, object oriented, or other type of database or data store.

A first data store that may be part of the vehicle control environment300 is a profile data store 252 for storing data about user profiles anddata associated with the users. A system data store 208 can include dataused by the vehicle control system 204 and/or one or more of thecomponents 324-352 to facilitate the functionality described herein. Thedata stores 208 and/or 252 may be as described in conjunction with FIGS.1 and/or 12A-12D.

The user interface/input interfaces 324 may be as described herein forproviding information or data and/or for receiving input or data from auser. Vehicle systems 328 can include any of the mechanical, electrical,electromechanical, computer, or other systems associated with thefunction of the vehicle 100. For example, vehicle systems 328 caninclude one or more of, but is not limited to, the steering system, thebraking system, the engine and engine control systems, the electricalsystem, the suspension, the drive train, the cruise control system, theradio, the heating, ventilation, air conditioning (HVAC) system, thewindows and/or doors, etc. These systems are well known in the art andwill not be described further.

Examples of the other systems and subsystems 324-352 may be as describedfurther herein. For example, the user interface(s)/input interface(s)324 may be as described in FIGS. 2 and 8B; the vehicle subsystems 328may be as described in FIG. 6 a et. seq.; the user interaction subsystem332 may be as described in conjunction with the user/device interactionsubsystem 817 of FIG. 8B; the Navigation subsystem 336 may be asdescribed in FIGS. 6A and 8C; the sensor(s)/sensor subsystem 340 may beas described in FIGS. 7A and 7B; the communication subsystem 344 may beas described in FIGS. 2, 4, 5B, 5C, and 9; the media subsystem 348 maybe as described in FIG. 8A; and, the device interaction subsystem 352may be as described in FIG. 2 and in conjunction with the user/deviceinteraction subsystem 817 of FIG. 8B.

FIG. 4 illustrates an optional communications channel architecture 400and associated communications components. FIG. 4 illustrates some of theoptional components that can be interconnected via the communicationchannels/zones 404. Communication channels/zones 404 can carryinformation on one or more of a wired and/or wireless communicationslink with, in the illustrated example, there being three communicationschannels/zones, 408, 412, and 416.

This optional environment 400 can also include an IP router 420, anoperator cluster 424, one or more storage devices 428, one or moreblades, such as master blade 432, and computational blades 436 and 440.Additionally, the communications channels/zones 404 can interconnect oneor more displays, such as, remote display 1 444, remote display N 448,and console display 452. The communications channels/zones 404 alsointerconnect an access point 456, a Bluetooth® access point/USB hub 460,a Femtocell 464, a storage controller 468, that is connected to one ormore of USB devices 472, DVDs 476, or other storage devices 480. Toassist with managing communications within the communication channel,the environment 400 optionally includes a firewall 484 which will bediscussed hereinafter in greater detail. Other components that couldalso share the communications channel/zones 404 include GPS 488, mediacontroller 492, which is connected to one or more media sources 496, andone or more subsystems, such as subsystem switches 498.

Optionally, the communications channels/zones 404 can be viewed as anI/O network or bus where the communications channels are carried on thesame physical media. Optionally, the communication channels 404 can besplit amongst one or more physical media and/or combined with one ormore wireless communications protocols. Optionally, the communicationschannels 404 can be based on wireless protocols with no physical mediainterconnecting the various elements described herein.

The environment 400 shown in FIG. 4 can include a collection of bladeprocessors that are housed in a “crate.” The crate can have a PC-stylebackplane connector 408 and a backplane Ethernet 408 that allows thevarious blades to communicate with one another using, for example, anEthernet.

Various other functional elements illustrated in FIG. 4 can beintegrated into this crate architecture with, as discussed hereinafter,various zones utilized for security. Optionally, as illustrated in FIG.4, the backplane 404/408 can have two separate Ethernet zones that mayor may not be on the same communications channel. Optionally, the zonesexist on a single communications channel on the I/O network/bus 408.Optionally, the zones are actually on different communications channels,e.g., 412, 416; however, the implementation is not restricted to anyparticular type of configuration. Rather, as illustrated in FIG. 4,there can be a red zone 417 and a green zone 413, and the I/O backplaneon the network/bus 408 that enables standard I/O operations. Thisbackplane or I/O network/bus 408 also optionally can provide powerdistribution to the various modules and blades illustrated in FIG. 4.The red and green Ethernet zones, 417 and 413 respectively, can beimplemented as Ethernet switches, with one on each side of the firewall484. Two Ethernets (untrusted and trusted) are not connected inaccordance with an optional embodiment. Optionally, the connectorgeometry for the firewall can be different for the Ethernet zones thanfor the blades that are a part of the system.

The red zone 417 only needs to go from the modular connector to theinput side of the backplane connector of the firewall 484. While FIG. 4indicates that there are five external red zone connectors to thefirewall 484, provisions can be made for any number of ports with theconnections being made at the access point 456, the Bluetooth® accesspoint (combo controller) 460, Femtocell 464, storage controller 468,and/or firewall 484. Optionally, the external port connections can bemade through a manufacturer configurable modular connector panel, andone or more of the red zone Ethernet ports could be available through acustomer supplied crate which allows, for example, wired Ethernetconnections from a bring-your-own-device (BYOD) to the firewall 484.

The green zone 413 goes from the output side of the firewall 484 andgenerally defines the trusted Ethernet. The Ethernet on the backplane408 essentially implements an Ethernet switch for the entire system,defining the Ethernet backbone of the vehicle 104. All other modules,e.g., blades, etc., can connect to a standard backplane bus and thetrusted Ethernet. Some number of switch ports can be reserved to connectto an output modular connector panel to distribute the Ethernetthroughout the vehicle 104, e.g., connecting such elements as theconsole display 452, remote displays 444, 448, GPS 488, etc. Optionally,only trusted components, either provided or approved by the manufacturerafter testing, can be attached to the green zone 413, which is bydefinition in the trusted Ethernet environment.

Optionally, the environment 400, shown in FIG. 4, utilizes IPv6 overEthernet connections wherever possible. Using, for example, the Broadcomsingle-twisted pair Ethernet technology, wiring harnesses are simplifiedand data transmission speeds are maximized. However, while the Broadcomsingle-twisted pair Ethernet technology can be used, in general, systemsand methods can work comparably well with any type of well-knownEthernet technology or other comparable communications technology.

As illustrated in FIG. 4 the I/O network/bus 408 is a split-bus conceptthat contains three independent bus structures:

-   -   The red zone 417—the untrusted Ethernet environment. This zone        417 may be used to connect network devices and customer provided        devices to the vehicle information system with these devices        being on the untrusted side of the firewall 484.    -   The green zone 413—the trusted Ethernet environment, this zone        413 can be used to connect manufacturer certified devices such        as GPS units, remote displays, subsystem switches, and the like,        to the vehicle network 404. Manufacturer certified devices can        be implemented by vendors that allow the vehicle software system        to validate whether or not a device is certified to operate with        the vehicle 100. Optionally, only certified devices are allowed        to connect to the trusted side of the network.    -   The I/O bus 409—the I/O bus may be used to provide power and        data transmission to bus-based devices such as the vehicle solid        state drive, the media controller blade 492, the computational        blades 436, 440, and the like.

As an example, the split-bus structure can have the following minimumconfiguration:

-   -   Two slots for the red zone Ethernet; One slot for built-in        LTE/WiMax access 420 from the car to other network resources        such as the cloud/Internet;    -   One slot for user devices or bring-your-own device access, this        slot can implement, for example, WiFi, Bluetooth®, and/or USB        connectivity 456, which can be provided in, for example, the        customer crate;    -   One slot for combined red zone and green zone Ethernet, this        slot can be reserved for the firewall controller;    -   Two slots for computational blades. Here the two computation        blades are illustratively as shown the optional master blade and        the multimedia blade or controller 492 which can be provided as        standard equipment; and    -   The expansion controller that allows the I/O bus to be extended        and provides additional Ethernet switch ports for one or more of        the red or green zones, which may require that the basic green        zone Ethernet switch implementation will support additional        ports beyond the initial three that are needed for the basic        exemplary system.    -   It should be possible to build 8 or 16 or more Ethernet switches        that allow for the expansion with existing component(s) in a        straight-forward manner.

The red zone 417 can be implemented as an 8-port Ethernet switch thathas three actual bus ports within the crate with the remaining fiveports being available on the customer crate. The crate implements redzone slots for the firewall controller 484, the combo controller whichincludes WiFi, Bluetooth®, USB hub (456, 460) and the IP router 420.

The firewall controller 484 can have a dedicated slot that bridges thered zone 417, green zone 413, and uses the I/O bus for powerconnections. In accordance with an optional low cost implementation, thefirewall 484 can be implemented by a dummy module that simply bridgesthe red zone 417 and the green zone 413 without necessarily providingany firewall functionality. The combo controller 460 that includes theWiFi, Bluetooth®, and USB hub can be provided for consumer deviceconnections. This controller can also implement the IPv6 (un-routable)protocol to insure that all information is packetized for transmissionvia IP over the Ethernet in the I/O network/bus 408.

The combo controller 460 with the USB hub can have ports in the customercrate. The combo controller 460 can implement USB discovery functionsand packetizes the information for transmission via IP over Ethernet.The combo controller 460 can also facilitate installation of the correctUSB driver for the discovered device, such as a BYOD from the user. Thecombo controller 460 and USB hub can then map the USB address to a“local” IPv6 address for interaction with one or more of thecomputational blades which is generally going to be the media controller492.

The IP router 420 can implement Internet access through a manufacturerprovided service. This service can allow, for example, a manufacturer tooffer value-added services to be integrated into the vehicle informationsystems. The existence of the manufacturer provided Internet access canalso allow the “e-Call” function and other vehicle data recorderfunctions to be implemented. IP router 420 also allows, for example,WiMax, 4G LTE, and other connections to the Internet through a serviceprovider that can be, for example, contracted by the manufacturer.Internally, the IP router 420 can allow cellular handset connections tothe Internet through a Femtocell 464 that is part of the IP routerimplementation. The IP router 420, with the Femtocell 464, can alsoallow a cone of silence functionality to be implemented. The IP router420 can be an optional component for a vehicle provided by, for example,the manufacturer, a dealer, or installed by a user. In the absence ofthe IP router 420, it is possible to connect a consumer handheld deviceto the I/O network/bus 408 using, for example, either WiFi or Bluetooth®456, 460. While functionality may be somewhat reduced when using ahandheld device instead of a built-in Ethernet connection, systems andmethods of this invention can also work utilizing this consumer handhelddevice which then connects to the Internet via, for example, WiMax, 4G,4G LTE, or the like.

FIGS. 5A-5C show configurations of a vehicle 104. In general, a vehicle104 may provide functionality based at least partially on one or moreareas, zones, and distances, associated with the vehicle 104.Non-limiting examples of this functionality are provided herein below.

An arrangement or configuration for sensors within a vehicle 104 is asshown in FIG. 5A. The sensor arrangement 500 can include one or moreareas 508 within the vehicle. An area can be a larger part of theenvironment inside or outside of the vehicle 104. Thus, area one 508Amay include the area within the trunk space or engine space of thevehicle 104 and/or the front passenger compartment. Area two 508B mayinclude a portion of the interior space 108 (e.g., a passengercompartment, etc.) of the vehicle 104. The area N, 508N, may include thetrunk space or rear compartment area, when included within the vehicle104. The interior space 108 may also be divided into other areas. Thus,one area may be associated with the front passenger's and driver'sseats, a second area may be associated with the middle passengers'seats, and a third area may be associated with a rear passenger's seat.Each area 508 may include one or more sensors that are positioned oroperate to provide environmental information about that area 508.

Each area 508 may be further separated into one or more zones 512 withinthe area 508. For example, area 1 508A may be separated into zone A512A, and zone B 512B. Each zone 512 may be associated with a particularportion of the interior occupied by a passenger. For example, zone A512A may be associated with a driver. Zone B 512B, may be associatedwith a front passenger. Each zone 512 may include one or more sensorsthat are positioned or configured to collect information about theenvironment or ecosystem associated with that zone or person.

A passenger area 508B may include more than two zones as described inconjunction with area 508A. For example, area 508B may include threezones, 512C, 512D, and 512E. These three separate zones 512C, 512D, and512E may be associated with three passenger seats typically found in therear passenger area of a vehicle 104. An area 508N and may include asingle zone 512N as there may be no separate passenger areas but mayinclude a single trunk area within the vehicle 104. The number of zones512 is unlimited within the areas as the areas are also unlimited insidethe vehicle 104. Further, it should be noted that there may be one orareas 508 or zones 512 that may be located outside the vehicle 104 thatmay have a specific set of sensors associated therewith.

Optionally, each area/access point 508, 456, 516, 520, and/or zone 512,associated with a vehicle 104, may comprise one or more sensors todetermine a presence of a user 216 and/or device 212, 248 in and/oradjacent to each area 508, 456, 516, 520, and/or zone 512. The sensorsmay include vehicle sensors 242 and/or non-vehicle sensors 236 asdescribed herein. It is anticipated that the sensors may be configuredto communicate with a vehicle control system 204 and/or the diagnosticcommunications module 256. Additionally or alternatively, the sensorsmay communicate with a device 212, 248. The communication of sensorswith the vehicle 104 may initiate and/or terminate the control of device212, 248 features. For example, a vehicle operator may be located in asecond outside area 520 associated with a vehicle 104. As the operatorapproaches the first outside area 516, associated with the vehicle 104,the vehicle control system 204 may determine to control featuresassociated with one or more device 212, 248 and diagnosticcommunications module 256.

Optionally, the location of the device 212, 248 relative to the vehicle104 may determine vehicle functionality and/or features to be providedand/or restricted to a user 216. By way of example, a device 212, 248associated with a user 216 may be located at a second outside area 520from the vehicle 104. In this case, and based at least partially on thedistance of the device 212, 248 from the vehicle 104 (e.g., provided bydetecting the device 212, 248 at or beyond the second outside area 520)the vehicle 104 may lock one or more features (e.g., ignition access,vehicle access, communications ability, etc.) associated with thevehicle 104. Optionally, the vehicle 104 may provide an alert based onthe distance of the device 212, 248 from the vehicle 104. Continuing theexample above, once the device 212, 248 reaches the first outside area516 of the vehicle 104 at least one of the vehicle features may beunlocked. For instance, by reaching the first outside area 516, thevehicle 104 may unlock a door of the vehicle 104. In some cases, whenthe device is detected to be inside the vehicle 104, the various sensors236, 242 may determine that the user 216 is in an area 508 and/or zone512. As is further described herein, features of the vehicle 104, device212, 248, and/or other components may be controlled based on rulesstored in a memory.

FIG. 5B illustrates optional internal vehicle communications between oneor more of the vehicle and one or more devices or between devices.Various communications can occur utilizing one or more Bluetooth®, NFC,WiFi, mobile hot spot, point-to-point communications,point-to-multipoint other point communications, an ad hoc network, or ingeneral any known communications protocol over any known communicationsmedia or media-types.

Optionally, various types of internal vehicle communications can befacilitated using an access point 456 that utilizes one or more ofBluetooth®, NFC, WiFi, wireless Ethernet, mobile hot spot technology, orthe like. Upon being connected with, and optionally authenticated to theaccess point 456, the connected device is able to communicate with oneor more of the vehicle and one or more other devices that are connectedto the access point 456. The type of connection to the access point 456can be based on, for example, the zone 512, in which the device islocated.

The user may identify their zone 512 in conjunction with anauthentication procedure to the access point 456. For example, a driverin zone A 512A, upon authenticating to the access point 456, can causethe access point 456 to send a query to the device asking the deviceuser in which zone 512 they are located. As discussed hereinafter, thezone 512 the user device is located in may have an impact on the type ofcommunications, available bandwidth, the types of other devices orvehicle systems or subsystems the device could communicate with, and thelike. As a brief introduction, internal communications with zone A 512Amay be given preferential treatment over those communicationsoriginating from area 2 508B, which could have in itself, preferentialtreatment over communications originating within area N 508N.

Moreover, the device in zone A 512A can include profile information thatgoverns the other devices that are allowed to connect to the accesspoint 456 and what those devices have access to, how they cancommunicate, how much bandwidth they are allocated, and the like. While,optionally, the device associated with zone A 512A will be consideredthe “master” controller of the profile that governs the internal vehiclecommunications, it should be appreciated that this was arbitrarilychosen since it is assumed that there will always be a driver in a carthat is present in zone A 512A. However, it should be appreciated thedriver in zone A 512A, for example, may not have a communications devicein which case a device associated with one of the other areas or zones,such as zone B 512B, area 2 508B, or area N 508N could also beassociated with or control this master profile.

Optionally, various devices located within the various zones 512 canconnect using, for example, ports provided by access point 456 orBluetooth® access point/USB hub 460 as illustrated in FIG. 4. Similarly,the device(s) could connect utilizing the Femtocell 464 and optionallybe directly connected via, for example, a standard Ethernet port.

As discussed, each one of the areas, area 1 508A, area 2 508B, and areaN 508N, can each have associated therewith a profile that governs, forexample, how many and what types of devices can connect from that area508, bandwidth allocated to that area 508, the types of media or contentavailable to device(s) within that area 508, the interconnection ofdevices within that area 508 or between areas 508, or, in general, cancontrol any aspect of communication of an associated device with any oneor more other associated devices/vehicle systems within the vehicle 104.

Optionally, area 2 508B devices can be provided with full access tomultimedia and infotainment available within the vehicle 104, however,devices in area 2 508B may be restricted from any access to vehiclefunctions. Only devices in area 1 508A may be able to access vehiclecontrol functions such as when “parents” are located in area 1 508A andthe children are located in area 2 508B. Optionally, devices found inzone E 512E of area 2 508B may be able to access limited vehicle controlfunctionality such as climate control within area 2. Similarly, devicesin area N 508N may be able to control climate features within zone N512N.

As will be appreciated, profiles can be established that allowmanagement of communications within each of the areas 508, and furtheroptionally within each of the zones 512. The profile can be granular innature controlling not only what type of devices can connect within eachzone 512, but how those devices can communicate with other devicesand/or the vehicle and types of information that can be communicated.

To assist with identifying a location of a device within a zone 512, anumber of different techniques can be utilized. One optional techniqueinvolves one or more of the vehicle sensors detecting the presence of anindividual within one of the zones 512. Upon detection of an individualin a zone 512, communications subsystems 344 and the access point 456can cooperate to not only associate the device within the zone 512 withthe access point 456 but to also determine the location of the devicewithin an area, and optionally within a zone 512. Once the device isestablished within a zone 512, a profile associated with the vehicle 104can store information identifying that device and/or a person andoptionally associating it with a particular zone 512 as a default. Asdiscussed, there can be a master profile optionally associated with thedevice in zone A 512A, this master profile can govern communicationswith the communications subsystems 340 and where communications withinvehicle 104 are to occur.

Some optional profiles are illustrated below where the Master Profilegoverns other device connectivity:

Master Profile:

Area 1 508A Area 2 508B Area N 508N Other All Communications AllowAccess to No Access Master Infotainment Profile acts as Firewall andRouter All Vehicle Controls Allow Area 2 Climate ControlSecondary Profile (e.g., device in Zone B 512B, Area 1 508A)

Area 1 508A Area 2 508B Area N 508N Other All Communications AllowAccess to Allow Access to Master Infotainment Infotainment Profile actsas Firewall and Router All Vehicle Controls Allow Area 2 Allow Area 2Climate Control Climate Control

Secondary Profile, Option 2

Area 1 508A Area 2 508B Area N 508N Other All Communications AllowAccess to Allow Access to Infotainment, Infotainment Internet AllVehicle Controls Allow Area 2 Allow Area 2 Except Driver- ClimateControl Climate Control centric Controls

Some optional profiles are illustrated below where the Area/Zone governsdevice connectivity:

Area 2 508B Profile:

Area 1 508A Area 2 508B Area N 508N Other No Communications Allow Accessto with Area 1 Devices Infotainment, Allow Access to Other Area 2 orZone N Devices, Internet No Vehicle Controls Allow Area 2 ClimateControl

Area N 508N Profile:

Area 1 508A Area 2 508B Area N 508N Other Communications Allow Access towith Area 1, Zone B Infotainment, Allow Device Access to Other Area N orZone N Devices No Vehicle Controls Allow Area N Climate Control

Area 2 508B Profile:

Area 1 508A Area 2 508B Area N 508N Other Media Sharing with AllowAccess to Area 1, Zone B and Infotainment, Allow Vehicle Access to OtherArea 2 or Zone N Devices, Internet and Femtocell No Vehicle Controls

Optionally, a user's device, such as a SmartPhone, can store in, forexample a profile, with which zone 512 the user's device is associated.Then, assuming the user sits in the same zone 512 and area 508 aspreviously, the user's device can re-establish the same communicationsprotocols with the access point 456 as were previously established.

In addition or in the alternative, the areas 508 and zones 512 can haveassociated therewith restrictions as to which one or more other user'sdevices with which users' devices can connect. For example, a firstuser's device can connect with any other user device in area 2 508B orarea N 508N, however is restricted from connecting with a user device inarea 1 508A, zone A 512A. However, the first user device may be able tocommunicate with another user's device that is located in area 1 508A,zone B 512B. These communications can include any type of standardcommunications such as sharing content, exchanging messages, forwardingor sharing multimedia or infotainment, or in general can include anycommunications that would ordinarily be available between two devicesand/or the vehicle and vehicle systems. As discussed, there may berestrictions on the type of communications that can be sent to thedevice in area 1 508A, zone A 512A. For example, the user's device inarea 1 508A, zone A 512A may be restricted from receiving one or more oftext messages, multimedia, infotainment, or in general anything that canbe envisioned as a potential distraction to the driver. Moreover, itshould be appreciated that the communications between the variousdevices and the various zones 512 need not necessarily occur with theassistance of access point 456, but the communications could also occurdirectly between the device(s).

FIG. 5C outlines optional internal vehicle communications between one ormore of the vehicle and one or more devices. More specifically, FIG. 5Cillustrates an example of vehicle communications where the vehicle 104is equipped with the necessary transceivers to provide a mobile hot spotfunctionality to any user device(s) therein, such as user devices 248Aand 248N.

Optionally, and as discussed above, one or more user devices can connectto the access point 456. This access point 456 is equipped to handlecommunications routing to not only the communication network/buses 224for intra-vehicle communications, but optionally can also communicatewith, for example, the Internet or the cloud, in cooperation withtransceiver 260. Optionally included is a firewall 484 that has thecapability of not only blocking certain types of content, such as amalicious content, but can also operate to exclude certain type ofcommunications from emanating from the vehicle 104 and transceiver 260.As will be appreciated, various profiles could be established in thefirewall 484 that controls not only the type of communications that canbe received at the vehicle 104, but the type of communications that canbe sent from the vehicle 104.

The transceiver 260 can be any type of well-known wireless transceiverthat communicates using a known communications protocol such as WiMax,4G, 4G LTE, 3G, or the like. The user devices can communicate via, forexample, WiFi link 248 with the access point 456, with the transceiver260 providing Internet connectivity to the various user devices. As willbe appreciated, there may need to be an account associated withtransceiver 260 with a wireless carrier to provide data and/or voiceconnectivity to enable the user devices to communicate with theInternet. Typically, the account is established on a month-to-monthbasis with an associated fee but could also be performed based on theamount of data to be transmitted, received, or in any other manner.

Moreover, one or more of the user's devices and access point 456 canmaintain profile information that governs how the user's devices areable to communicate with other devices, and optionally the Internet.Optionally, a profile can exist that only allows the user's devices tocommunicate with other user's devices and/or the vehicle, multimediaand/or the vehicle infotainment system, and may not be allowed access tothe Internet via transceiver 260. The profile can stipulate that theuser's device could connect to the Internet via transceiver 260 for aspecified period of time and/or up to a certain amount of data usage.The user's device can have full access to the Internet via transceiver260 with no limit on time or data usage which would reduce the datausage of the user's device since it is connected via WiFi to the accesspoint 456, but however, would increase the data usage by transceiver260, and therefore, shift the billing for that data usage to thetransceiver 260 instead of the user's device. Still further, and aspreviously discussed, the various profiles may stipulate which user'sdevice has priority for use of the bandwidth provided by the transceiver260. For example, a user's device located area 1 508A, zone A 512A maybe given preferential routing treatment of data above that of a user'sdevice in zone N 512N. In this manner, for example, a driver would begiven priority for Internet access above that of the passengers. Thiscould become important, for example, when the driver is trying to obtaintraffic or direction information or, for example, when the vehicle isperforming a download to update various software features.

As will be appreciated, the optional firewall 484 can cooperate with theaccess point 456 and the various profiles that area 508 associated withthe various devices within the vehicle 104 and can fully implementcommunications restrictions, control bandwidth limits, Internetaccessibility, malicious software blocking, and the like. Moreover, theoptional firewall 484 can be accessed by an administrator with one ormore of these configuration settings edited through an administrator'scontrol panel. For example, in a scenario where parents are always inarea 1 508A, it may be appropriate to give all of the user's devices inarea 1 508A full access to the Internet utilizing transceiver 260,however, while restricting access and/or bandwidth to any other userdevices within the vehicle 104. As the user's device and profile wouldbe known by the firewall 484, upon the user's device being associatedwith the access point 456, the firewall 484 and transceiver 260 can beconfigured to allow communications in accordance with the storedprofile.

A set of sensors or vehicle components 600 associated with the vehicle104 may be as shown in FIG. 6A. The vehicle 104 can include, among manyother components common to vehicles, wheels 607, a power source 609(such as an engine, motor, or energy storage system (e.g., battery orcapacitive energy storage system)), a manual or automatic transmission612, a manual or automatic transmission gear controller 616, a powercontroller 620 (such as a throttle), a vehicle control system 204, thedisplay device 212, a braking system 636, a steering wheel 640, a powersource activation/deactivation switch 644 (e.g., an ignition), anoccupant seating system 648, a wireless signal receiver 653 to receivewireless signals from signal sources such as roadside beacons and otherelectronic roadside devices, and a satellite positioning system receiver657 (e.g., a Global Positioning System (“GPS”) (US), GLONASS (Russia),Galileo positioning system (EU), Compass navigation system (China), andRegional Navigational Satellite System (India) receiver), driverlesssystems (e.g., cruise control systems, automatic steering systems,automatic braking systems, etc.).

The vehicle 104 can include a number of sensors in wireless or wiredcommunication with the vehicle control system 204 and/or display device212, 248 to collect sensed information regarding the vehicle state,configuration, and/or operation. Exemplary sensors may include one ormore of, but are not limited to, wheel state sensor 660 to sense one ormore of vehicle speed, acceleration, deceleration, wheel rotation, wheelspeed (e.g., wheel revolutions-per-minute), wheel slip, and the like, apower source energy output sensor 664 to sense a power output of thepower source 609 by measuring one or more of current engine speed (e.g.,revolutions-per-minute), energy input and/or output (e.g., voltage,current, fuel consumption, and torque) (e.g., turbine speed sensor,input speed sensor, crankshaft position sensor, manifold absolutepressure sensor, mass flow sensor, and the like), and the like, a switchstate sensor 668 to determine a current activation or deactivation stateof the power source activation/deactivation switch 644, a transmissionsetting sensor 670 to determine a current setting of the transmission(e.g., gear selection or setting), a gear controller sensor 672 todetermine a current setting of the gear controller 616, a powercontroller sensor 674 to determine a current setting of the powercontroller 620, a brake sensor 676 to determine a current state (brakingor non-braking) of the braking system 636, a seating system sensor 678to determine a seat setting and current weight of seated occupant, ifany) in a selected seat of the seating system 648, exterior and interiorsound receivers 690 and 692 (e.g., a microphone, sonar, and other typeof acoustic-to-electric transducer or sensor) to receive and convertsound waves into an equivalent analog or digital signal. Examples ofother sensors (not shown) that may be employed include safety systemstate sensors to determine a current state of a vehicular safety system(e.g., air bag setting (deployed or underplayed) and/or seat beltsetting (engaged or not engaged)), light setting sensor (e.g., currentheadlight, emergency light, brake light, parking light, fog light,interior or passenger compartment light, and/or tail light state (on oroff)), brake control (e.g., pedal) setting sensor, accelerator pedalsetting or angle sensor, clutch pedal setting sensor, emergency brakepedal setting sensor, door setting (e.g., open, closed, locked orunlocked) sensor, engine temperature sensor, passenger compartment orcabin temperature sensor, window setting (open or closed) sensor, one ormore interior-facing or exterior-facing cameras or other imaging sensors(which commonly convert an optical image into an electronic signal butmay include other devices for detection objects such as anelectromagnetic radiation emitter/receiver that emits electromagneticradiation and receives electromagnetic waves reflected by the object) tosense objects, such as other vehicles and pedestrians and optionallydetermine the distance, trajectory and speed of such objects, in thevicinity or path of the vehicle, odometer reading sensor, trip mileagereading sensor, wind speed sensor, radar transmitter/receiver output,brake wear sensor, steering/torque sensor, oxygen sensor, ambientlighting sensor, vision system sensor, ranging sensor, parking sensor,heating, venting, and air conditioning (HVAC) sensor, water sensor,air-fuel ratio meter, blind spot monitor, hall effect sensor,microphone, radio frequency (RF) sensor, infrared (IR) sensor, vehiclecontrol system sensors, wireless network sensor (e.g., Wi-Fi and/orBluetooth® sensor), cellular data sensor, and other sensors eitherfuture-developed or known to those of skill in the vehicle art.

In the depicted vehicle embodiment, the various sensors can be incommunication with the display device 212, 248 and vehicle controlsystem 204 via signal carrier network 224. As noted, the signal carriernetwork 224 can be a network of signal conductors, a wireless network(e.g., a radio frequency, microwave, or infrared communication systemusing a communications protocol, such as Wi-Fi), or a combinationthereof. The vehicle control system 204 may also provide signalprocessing of one or more sensors, sensor fusion of similar and/ordissimilar sensors, signal smoothing in the case of erroneous “wildpoint” signals, and/or sensor fault detection. For example, rangingmeasurements provided by one or more RF sensors may be combined withranging measurements from one or more IR sensors to determine one fusedestimate of vehicle range to an obstacle target.

The control system 204 may receive and read sensor signals, such aswheel and engine speed signals, as a digital input comprising, forexample, a pulse width modulated (PWM) signal. The processor 304 can beconfigured, for example, to read each of the signals into a portconfigured as a counter or configured to generate an interrupt onreceipt of a pulse, such that the processor 304 can determine, forexample, the engine speed in revolutions per minute (RPM) and the speedof the vehicle in miles per hour (MPH) and/or kilometers per hour (KPH).One skilled in the art will recognize that the two signals can bereceived from existing sensors in a vehicle comprising a tachometer anda speedometer, respectively. Alternatively, the current engine speed andvehicle speed can be received in a communication packet as numericvalues from a conventional dashboard subsystem comprising a tachometerand a speedometer. The transmission speed sensor signal can be similarlyreceived as a digital input comprising a signal coupled to a counter orinterrupt signal of the processor 304 or received as a value in acommunication packet on a network or port interface from an existingsubsystem of the vehicle 104. The ignition sensor signal can beconfigured as a digital input, wherein a HIGH value represents that theignition is on and a LOW value represents that the ignition is OFF.Three bits of the port interface can be configured as a digital input toreceive the gear shift position signal, representing eight possible gearshift positions. Alternatively, the gear shift position signal can bereceived in a communication packet as a numeric value on the portinterface. The throttle position signal can be received as an analoginput value, typically in the range 0-5 volts. Alternatively, thethrottle position signal can be received in a communication packet as anumeric value on the port interface. The output of other sensors can beprocessed in a similar fashion.

Other sensors may be included and positioned in the interior space 108of the vehicle 104. Generally, these interior sensors obtain data aboutthe health of the driver and/or passenger(s), data about the safety ofthe driver and/or passenger(s), and/or data about the comfort of thedriver and/or passenger(s). The health data sensors can include sensorsin the steering wheel that can measure various health telemetry for theperson (e.g., heart rate, temperature, blood pressure, blood presence,blood composition, etc.). Sensors in the seats may also provide forhealth telemetry (e.g., presence of liquid, weight, weight shifts,etc.). Infrared sensors could detect a person's temperature; opticalsensors can determine a person's position and whether the person hasbecome unconscious. Other health sensors are possible and includedherein.

Safety sensors can measure whether the person is acting safely. Opticalsensors can determine a person's position and focus. If the person stopslooking at the road ahead, the optical sensor can detect the lack offocus. Sensors in the seats may detect if a person is leaning forward ormay be injured by a seat belt in a collision. Other sensors can detectthat the driver has at least one hand on a steering wheel. Other safetysensors are possible and contemplated as if included herein.

Comfort sensors can collect information about a person's comfort.Temperature sensors may detect a temperature of the interior cabin.Moisture sensors can determine a relative humidity. Audio sensors candetect loud sounds or other distractions. Audio sensors may also receiveinput from a person through voice data. Other comfort sensors arepossible and contemplated as if included herein.

FIG. 6B shows an interior sensor configuration for one or more zones 512of a vehicle 104 optionally. Optionally, the areas 508 and/or zones 512of a vehicle 104 may include sensors that are configured to collectinformation associated with the interior 108 of a vehicle 104. Inparticular, the various sensors may collect environmental information,user information, and safety information, to name a few. Embodiments ofthese sensors may be as described in conjunction with FIGS. 7A-8B.

Optionally, the sensors may include one or more of optical, or image,sensors 622A-B (e.g., cameras, etc.), motion sensors 624A-B (e.g.,utilizing RF, IR, and/or other sound/image sensing, etc.), steeringwheel user sensors 642 (e.g., heart rate, temperature, blood pressure,sweat, health, etc.), seat sensors 677 (e.g., weight, load cell,moisture, electrical, force transducer, etc.), safety restraint sensors679 (e.g., seatbelt, airbag, load cell, force transducer, etc.),interior sound receivers 692A-B, environmental sensors 694 (e.g.,temperature, humidity, air, oxygen, etc.), and the like.

The image sensors 622A-B may be used alone or in combination to identifyobjects, users 216, and/or other features, inside the vehicle 104.Optionally, a first image sensor 622A may be located in a differentposition within a vehicle 104 from a second image sensor 622B. When usedin combination, the image sensors 622A-B may combine captured images toform, among other things, stereo and/or three-dimensional (3D) images.The stereo images can be recorded and/or used to determine depthassociated with objects and/or users 216 in a vehicle 104. Optionally,the image sensors 622A-B used in combination may determine the complexgeometry associated with identifying characteristics of a user 216. Forinstance, the image sensors 622A-B may be used to determine dimensionsbetween various features of a user's face (e.g., the depth/distance froma user's nose to a user's cheeks, a linear distance between the centerof a user's eyes, and more). These dimensions may be used to verify,record, and even modify characteristics that serve to identify a user216. As can be appreciated, utilizing stereo images can allow for a user216 to provide complex gestures in a 3D space of the vehicle 104. Thesegestures may be interpreted via one or more of the subsystems asdisclosed herein. Optionally, the image sensors 622A-B may be used todetermine movement associated with objects and/or users 216 within thevehicle 104. It should be appreciated that the number of image sensorsused in a vehicle 104 may be increased to provide greater dimensionalaccuracy and/or views of a detected image in the vehicle 104.

The vehicle 104 may include one or more motion sensors 624A-B. Thesemotion sensors 624A-B may detect motion and/or movement of objectsinside the vehicle 104. Optionally, the motion sensors 624A-B may beused alone or in combination to detect movement. For example, a user 216may be operating a vehicle 104 (e.g., while driving, etc.) when apassenger in the rear of the vehicle 104 unbuckles a safety belt andproceeds to move about the vehicle 104. In this example, the movement ofthe passenger could be detected by the motion sensors 624A-B.Optionally, the user 216 could be alerted of this movement by one ormore of the devices 212, 248 in the vehicle 104. In another example, apassenger may attempt to reach for one of the vehicle control features(e.g., the steering wheel 640, the console, icons displayed on the headunit and/or device 212, 248, etc.). In this case, the movement (i.e.,reaching) of the passenger may be detected by the motion sensors 624A-B.Optionally, the path, trajectory, anticipated path, and/or some otherdirection of movement/motion may be determined using the motion sensors624A-B. In response to detecting the movement and/or the directionassociated with the movement, the passenger may be prevented frominterfacing with and/or accessing at least some of the vehicle controlfeatures (e.g., the features represented by icons may be hidden from auser interface, the features may be locked from use by the passenger,combinations thereof, etc.). As can be appreciated, the user 216 may bealerted of the movement/motion such that the user 216 can act to preventthe passenger from interfering with the vehicle 104 controls.Optionally, the number of motion sensors in a vehicle 104, or areas of avehicle 104, may be increased to increase an accuracy associated withmotion detected in the vehicle 104.

The interior sound receivers 692A-B may include, but are not limited to,microphones and other types of acoustic-to-electric transducers orsensors. Optionally, the interior sound receivers 692A-B may beconfigured to receive and convert sound waves into an equivalent analogor digital signal. The interior sound receivers 692A-B may serve todetermine one or more locations associated with various sounds in thevehicle 104. The location of the sounds may be determined based on acomparison of volume levels, intensity, and the like, between soundsdetected by two or more interior sound receivers 692A-B. For instance, afirst interior sound receiver 692A may be located in a first area of thevehicle 104 and a second interior sound receiver 692B may be located ina second area of the vehicle 104. If a sound is detected at a firstvolume level by the first interior sound receiver 692A and a second,higher, volume level by the second interior sound receiver 692B in thesecond area of the vehicle 104, the sound may be determined to be closerto the second area of the vehicle 104. As can be appreciated, the numberof sound receivers used in a vehicle 104 may be increased (e.g., morethan two, etc.) to increase measurement accuracy surrounding sounddetection and location, or source, of the sound (e.g., viatriangulation, etc.).

Seat sensors 677 may be included in the vehicle 104. The seat sensors677 may be associated with each seat and/or zone 512 in the vehicle 104.Optionally, the seat sensors 677 may provide health telemetry and/oridentification via one or more of load cells, force transducers, weightsensors, moisture detection sensor, electrical conductivity/resistancesensor, and the like. For example, the seat sensors 677 may determinethat a user 216 weighs 180 lbs. This value may be compared to user datastored in memory to determine whether a match exists between thedetected weight and a user 216 associated with the vehicle 104. Inanother example, if the seat sensors 677 detect that a user 216 isfidgeting, or moving, in a seemingly uncontrollable manner, the systemmay determine that the user 216 has suffered a nervous and/or muscularsystem issue (e.g., seizure, etc.). The vehicle control system 204 maythen cause the vehicle 104 to slow down and in addition or alternativelythe automobile controller 8104 (described below) can safely take controlof the vehicle 104 and bring the vehicle 104 to a stop in a safelocation (e.g., out of traffic, off a freeway, etc).

Health telemetry and other data may be collected via the steering wheeluser sensors 642. Optionally, the steering wheel user sensors 642 maycollect heart rate, temperature, blood pressure, and the like,associated with a user 216 via at least one contact disposed on or aboutthe steering wheel 640.

The safety restraint sensors 679 may be employed to determine a stateassociated with one or more safety restraint devices in a vehicle 104.The state associated with one or more safety restraint devices may serveto indicate a force observed at the safety restraint device, a state ofactivity (e.g., retracted, extended, various ranges of extension and/orretraction, deployment, buckled, unbuckled, etc.), damage to the safetyrestraint device, and more.

Environmental sensors 694, including one or more of temperature,humidity, air, oxygen, carbon monoxide, smoke, and other environmentalcondition sensors may be used in a vehicle 104. These environmentalsensors 694 may be used to collect data relating to the safety, comfort,and/or condition of the interior space 108 of the vehicle 104. Amongother things, the data collected by the environmental sensors 694 may beused by the vehicle control system 204 to alter functions of a vehicle.The environment may correspond to an interior space 108 of a vehicle 104and/or specific areas 508 and/or zones 512 of the vehicle 104. It shouldbe appreciate that an environment may correspond to a user 216. Forexample, a low oxygen environment may be detected by the environmentalsensors 694 and associated with a user 216 who is operating the vehicle104 in a particular zone 512. In response to detecting the low oxygenenvironment, at least one of the subsystems of the vehicle 104, asprovided herein, may alter the environment, especially in the particularzone 512, to increase the amount of oxygen in the zone 512. Additionallyor alternatively, the environmental sensors 694 may be used to reportconditions associated with a vehicle (e.g., fire detected, low oxygen,low humidity, high carbon monoxide, etc.). The conditions may bereported to a user 216 and/or a third party via at least onecommunications module as provided herein.

Among other things, the sensors as disclosed herein may communicate witheach other, with devices 212, 248, and/or with the vehicle controlsystem 204 via the signal carrier network 224. Additionally oralternatively, the sensors disclosed herein may serve to provide datarelevant to more than one category of sensor information including, butnot limited to, combinations of environmental information, userinformation, and safety information to name a few.

FIGS. 7A-7B show block diagrams of various sensors that may beassociated with a vehicle 104. Although depicted as interior andexterior sensors, it should be appreciated that any of the one or moreof the sensors shown may be used in both the interior space 108 and theexterior space of the vehicle 104. Moreover, sensors having the samesymbol or name may include the same, or substantially the same,functionality as those sensors described elsewhere in the presentdisclosure. Further, although the various sensors are depicted inconjunction with specific groups (e.g., environmental 708, 708E, userinterface 712, safety 716, 716E, etc.) the sensors should not be limitedto the groups in which they appear. In other words, the sensors may beassociated with other groups or combinations of groups and/ordisassociated from one or more of the groups shown. The sensors asdisclosed herein may communicate with each other, the devices 212, 248,and/or the vehicle control system 204 via one or more communicationschannel(s) 356.

FIG. 7A is a block diagram of an embodiment of interior sensors 340 fora vehicle 104 is provided. The interior sensors 340 may be arranged intoone or more groups, based at least partially on the function of theinterior sensors 340. The interior space 108 of a vehicle 104 mayinclude an environmental group 708, a user interface group 712, and asafety group 716. Additionally or alternatively, there may be sensorsassociated with various devices inside the vehicle (e.g., devices 212,248, smart phones, tablets, mobile computers, etc.)

The environmental group 708 may comprise sensors configured to collectdata relating to the internal environment of a vehicle 104. It isanticipated that the environment of the vehicle 104 may be subdividedinto areas 508 and zones 512 in an interior space 108 of a vehicle 104.In this case, each area 508 and/or zone 512 may include one or more ofthe environmental sensors. Examples of environmental sensors associatedwith the environmental group 708 may include, but are not limited to,oxygen/air sensors 724, temperature sensors 728, humidity sensors 732,light/photo sensors 736, and more. The oxygen/air sensors 724 may beconfigured to detect a quality of the air in the interior space 108 ofthe vehicle 104 (e.g., ratios and/or types of gasses comprising the airinside the vehicle 104, dangerous gas levels, safe gas levels, etc.).Temperature sensors 728 may be configured to detect temperature readingsof one or more objects, users 216, and/or areas 508 of a vehicle 104.Humidity sensors 732 may detect an amount of water vapor present in theair inside the vehicle 104. The light/photo sensors 736 can detect anamount of light present in the vehicle 104. Further, the light/photosensors 736 may be configured to detect various levels of lightintensity associated with light in the vehicle 104.

The user interface group 712 may comprise sensors configured to collectdata relating to one or more users 216 in a vehicle 104. As can beappreciated, the user interface group 712 may include sensors that areconfigured to collect data from users 216 in one or more areas 508 andzones 512 of the vehicle 104. For example, each area 508 and/or zone 512of the vehicle 104 may include one or more of the sensors in the userinterface group 712. Examples of user interface sensors associated withthe user interface group 712 may include, but are not limited to,infrared sensors 740, motion sensors 744, weight sensors 748, wirelessnetwork sensors 752, biometric sensors 756, camera (or image) sensors760, audio sensors 764, and more.

Infrared sensors 740 may be used to measure IR light irradiating from atleast one surface, user 216, or other object in the vehicle 104. Amongother things, the Infrared sensors 740 may be used to measuretemperatures, form images (especially in low light conditions), identifyusers 216, and even detect motion in the vehicle 104.

The motion sensors 744 may be similar to the motion detectors 624A-B, asdescribed in conjunction with FIG. 6B. Weight sensors 748 may beemployed to collect data relating to objects and/or users 216 in variousareas 508 of the vehicle 104. In some cases, the weight sensors 748 maybe included in the seats and/or floor of a vehicle 104.

Optionally, the vehicle 104 may include a wireless network sensor 752.This sensor 752 may be configured to detect one or more wirelessnetwork(s) inside the vehicle 104. Examples of wireless networks mayinclude, but are not limited to, wireless communications utilizingBluetooth®, Wi-Fi™, ZigBee, IEEE 802.11, and other wireless technologystandards. For example, a mobile hotspot may be detected inside thevehicle 104 via the wireless network sensor 752. In this case, thevehicle 104 may determine to utilize and/or share the mobile hotspotdetected via/with one or more other devices 212, 248 and/or componentsassociated with the vehicle 104.

Biometric sensors 756 may be employed to identify and/or recordcharacteristics associated with a user 216. It is anticipated thatbiometric sensors 756 can include at least one of image sensors, IRsensors, fingerprint readers, weight sensors, load cells, forcetransducers, heart rate monitors, blood pressure monitors, and the likeas provided herein.

The camera sensors 760 may be similar to image sensors 622A-B, asdescribed in conjunction with FIG. 6B. Optionally, the camera sensorsmay record still images, video, and/or combinations thereof. The audiosensors 764 may be similar to the interior sound receivers 692A-B, asdescribed in conjunction with FIGS. 6A-6B. The audio sensors may beconfigured to receive audio input from a user 216 of the vehicle 104.The audio input from a user 216 may correspond to voice commands,conversations detected in the vehicle 104, phone calls made in thevehicle 104, and/or other audible expressions made in the vehicle 104.

The safety group 716 may comprise sensors configured to collect datarelating to the safety of a user 216 and/or one or more components of avehicle 104. The vehicle 104 may be subdivided into areas 508 and/orzones 512 in an interior space 108 of a vehicle 104 where each area 508and/or zone 512 may include one or more of the safety sensors providedherein. Examples of safety sensors associated with the safety group 716may include, but are not limited to, force sensors 768, mechanicalmotion sensors 772, orientation sensors 776, restraint sensors 780, andmore.

The force sensors 768 may include one or more sensors inside the vehicle104 configured to detect a force observed in the vehicle 104. Oneexample of a force sensor 768 may include a force transducer thatconverts measured forces (e.g., force, weight, pressure, etc.) intooutput signals.

Mechanical motion sensors 772 may correspond to encoders,accelerometers, damped masses, and the like. Optionally, the mechanicalmotion sensors 772 may be adapted to measure the force of gravity (i.e.,G-force) as observed inside the vehicle 104. Measuring the G-forceobserved inside a vehicle 104 can provide valuable information relatedto a vehicle's acceleration, deceleration, collisions, and/or forcesthat may have been suffered by one or more users 216 in the vehicle 104.As can be appreciated, the mechanical motion sensors 772 can be locatedin an interior space 108 or an exterior of the vehicle 104.

Orientation sensors 776 can include accelerometers, gyroscopes, magneticsensors, and the like that are configured to detect an orientationassociated with the vehicle 104. Similar to the mechanical motionsensors 772, the orientation sensors 776 can be located in an interiorspace 108 or an exterior of the vehicle 104.

The restraint sensors 780 may be similar to the safety restraint sensors679 as described in conjunction with FIGS. 6A-6B. These sensors 780 maycorrespond to sensors associated with one or more restraint devicesand/or systems in a vehicle 104. Seatbelts and airbags are examples ofrestraint devices and/or systems. As can be appreciated, the restraintdevices and/or systems may be associated with one or more sensors thatare configured to detect a state of the device/system. The state mayinclude extension, engagement, retraction, disengagement, deployment,and/or other electrical or mechanical conditions associated with thedevice/system.

The associated device sensors 720 can include any sensors that areassociated with a device 212, 248 in the vehicle 104. As previouslystated, typical devices 212, 248 may include smart phones, tablets,laptops, mobile computers, and the like. It is anticipated that thevarious sensors associated with these devices 212, 248 can be employedby the vehicle control system 204. For example, a typical smart phonecan include, an image sensor, an IR sensor, audio sensor, gyroscope,accelerometer, wireless network sensor, fingerprint reader, and more. Itis an aspect of the present disclosure that one or more of theseassociated device sensors 720 may be used by one or more subsystems ofthe vehicle system 200.

In FIG. 7B, a block diagram of an embodiment of exterior sensors 340 fora vehicle 104 is shown. The exterior sensors may include sensors thatare identical, or substantially similar, to those previously disclosedin conjunction with the interior sensors of FIG. 7A. Optionally, theexterior sensors 340 may be configured to collect data relating to oneor more conditions, objects, users 216, and other events that areexternal to the interior space 108 of the vehicle 104. For instance, theoxygen/air sensors 724 may measure a quality and/or composition of theair outside of a vehicle 104. As another example, the motion sensors 744may detect motion outside of a vehicle 104.

The external environmental group 708E may comprise sensors configured tocollect data relating to the external environment of a vehicle 104. Inaddition to including one or more of the sensors previously described,the external environmental group 708E may include additional sensors,such as, vehicle sensors 750, biological sensors, and wireless signalsensors 758. Vehicle sensors 750 can detect vehicles that are in anenvironment surrounding the vehicle 104. For example, the vehiclesensors 750 may detect vehicles in a first outside area 516, a secondoutside area 520, and/or combinations of the first and second outsideareas 516, 520. Optionally, the vehicle sensors 750 may include one ormore of RF sensors, IR sensors, image sensors, and the like to detectvehicles, people, hazards, etc. that are in an environment exterior tothe vehicle 104. Additionally or alternatively, the vehicle sensors 750can provide distance/directional information relating to a distance(e.g., distance from the vehicle 104 to the detected object) and/or adirection (e.g., direction of travel, etc.) associated with the detectedobject.

The biological sensors 754 may determine whether one or more biologicalentities (e.g., an animal, a person, a user 216, etc.) is in an externalenvironment of the vehicle 104. Additionally or alternatively, thebiological sensors 754 may provide distance information relating to adistance of the biological entity from the vehicle 104. Biologicalsensors 754 may include at least one of RF sensors, IR sensors, imagesensors and the like that are configured to detect biological entities.For example, an IR sensor may be used to determine that an object, orbiological entity, has a specific temperature, temperature pattern, orheat signature. Continuing this example, a comparison of the determinedheat signature may be compared to known heat signatures associated withrecognized biological entities (e.g., based on shape, locations oftemperature, and combinations thereof, etc.) to determine whether theheat signature is associated with a biological entity or an inanimate,or non-biological, object.

The wireless signal sensors 758 may include one or more sensorsconfigured to receive wireless signals from signal sources such asWi-Fi™ hotspots, cell towers, roadside beacons, other electronicroadside devices, and satellite positioning systems. Optionally, thewireless signal sensors 758 may detect wireless signals from one or moreof a mobile phone, mobile computer, keyless entry device, RFID device,near field communications (NFC) device, and the like.

The external safety group 716E may comprise sensors configured tocollect data relating to the safety of a user 216 and/or one or morecomponents of a vehicle 104. Examples of safety sensors associated withthe external safety group 716E may include, but are not limited to,force sensors 768, mechanical motion sensors 772, orientation sensors776, vehicle body sensors 782, and more. Optionally, the exterior safetysensors 716E may be configured to collect data relating to one or moreconditions, objects, vehicle components, and other events that areexternal to the vehicle 104. For instance, the force sensors 768 in theexternal safety group 716E may detect and/or record force informationassociated with the outside of a vehicle 104. For instance, if an objectstrikes the exterior of the vehicle 104, the force sensors 768 from theexterior safety group 716E may determine a magnitude, location, and/ortime associated with the strike.

The vehicle 104 may include a number of vehicle body sensors 782. Thevehicle body sensors 782 may be configured to measure characteristicsassociated with the body (e.g., body panels, components, chassis,windows, etc.) of a vehicle 104. For example, two vehicle body sensors782, including a first body sensor and a second body sensor, may belocated at some distance apart. Continuing this example, the first bodysensor may be configured to send an electrical signal across the body ofthe vehicle 104 to the second body sensor, or vice versa. Upon receivingthe electrical signal from the first body sensor, the second body sensormay record a detected current, voltage, resistance, and/or combinationsthereof associated with the received electrical signal. Values (e.g.,current, voltage, resistance, etc.) for the sent and received electricalsignal may be stored in a memory. These values can be compared todetermine whether subsequent electrical signals sent and receivedbetween vehicle body sensors 782 deviate from the stored values. Whenthe subsequent signal values deviate from the stored values, thedifference may serve to indicate damage and/or loss of a body component.Additionally or alternatively, the deviation may indicate a problem withthe vehicle body sensors 782. The vehicle body sensors 782 maycommunicate with each other, a vehicle control system 204, and/orsystems of the vehicle system 200 via a communications channel 356.Although described using electrical signals, it should be appreciatedthat alternative embodiments of the vehicle body sensors 782 may usesound waves and/or light to perform a similar function.

FIG. 8A is a block diagram of an embodiment of a media controllersubsystem 348 for a vehicle 104. The media controller subsystem 348 mayinclude, but is not limited to, a media controller 804, a mediaprocessor 808, a match engine 812, an audio processor 816, a speechsynthesis module 820, a network transceiver 824, a signal processingmodule 828, memory 832, and a language database 836. Optionally, themedia controller subsystem 348 may be configured as a dedicated bladethat implements the media-related functionality of the system 200.Additionally or alternatively, the media controller subsystem 348 canprovide voice input, voice output, library functions for multimedia, anddisplay control for various areas 508 and/or zones 512 of the vehicle104.

Optionally, the media controller subsystem 348 may include a local IPaddress (e.g., IPv4, IPv6, combinations thereof, etc.) and even aroutable, global unicast address. The routable, global unicast addressmay allow for direct addressing of the media controller subsystem 348for streaming data from Internet resources (e.g., cloud storage, useraccounts, etc.). It is anticipated, that the media controller subsystem348 can provide multimedia via at least one Internet connection, orwireless network communications module, associated with the vehicle 104.Moreover, the media controller subsystem 348 may be configured toservice multiple independent clients simultaneously.

The media processor 808 may comprise a general purpose programmableprocessor or controller for executing application programming orinstructions related to the media subsystem 348. The media processor 808may include multiple processor cores, and/or implement multiple virtualprocessors. Optionally, the media processor 808 may include multiplephysical processors. By way of example, the media processor 808 maycomprise a specially configured application specific integrated circuit(ASIC) or other integrated circuit, a digital signal processor, acontroller, a hardwired electronic or logic circuit, a programmablelogic device or gate array, a special purpose computer, or the like. Themedia processor 808 generally functions to run programming code orinstructions implementing various functions of the media controller 804.

The match engine 812 can receive input from one or more components ofthe vehicle system 800 and perform matching functions. Optionally, thematch engine 812 may receive audio input provided via a microphone 886of the system 800. The audio input may be provided to the mediacontroller subsystem 348 where the audio input can be decoded andmatched, via the match engine 812, to one or more functions available tothe vehicle 104. Similar matching operations may be performed by thematch engine 812 relating to video input received via one or more imagesensors, cameras 878, and the like.

The media controller subsystem 348 may include a speech synthesis module820 configured to provide audio output to one or more speakers 880, oraudio output devices, associated with the vehicle 104. Optionally, thespeech synthesis module 820 may be configured to provide audio outputbased at least partially on the matching functions performed by thematch engine 812.

As can be appreciated, the coding/decoding, the analysis of audioinput/output, and/or other operations associated with the match engine812 and speech synthesis module 820, may be performed by the mediaprocessor 808 and/or a dedicated audio processor 816. The audioprocessor 816 may comprise a general purpose programmable processor orcontroller for executing application programming or instructions relatedto audio processing. Further, the audio processor 816 may be similar tothe media processor 808 described herein.

The network transceiver 824 can include any device configured totransmit and receive analog and/or digital signals. Optionally, themedia controller subsystem 348 may utilize a network transceiver 824 inone or more communication networks associated with the vehicle 104 toreceive and transmit signals via the communications channel 356.Additionally or alternatively, the network transceiver 824 may acceptrequests from one or more devices 212, 248 to access the mediacontroller subsystem 348. One example of the communication network is alocal-area network (LAN). As can be appreciated, the functionalityassociated with the network transceiver 824 may be built into at leastone other component of the vehicle 104 (e.g., a network interface card,communications module, etc.).

The signal processing module 828 may be configured to alteraudio/multimedia signals received from one or more input sources (e.g.,microphones 886, etc.) via the communications channel 356. Among otherthings, the signal processing module 828 may alter the signals receivedelectrically, mathematically, combinations thereof, and the like.

The media controller 804 may also include memory 832 for use inconnection with the execution of application programming or instructionsby the media processor 808, and for the temporary or long term storageof program instructions and/or data. As examples, the memory 832 maycomprise RAM, DRAM, SDRAM, or other solid state memory.

The language database 836 may include the data and/or libraries for oneor more languages, as are used to provide the language functionality asprovided herein. In one case, the language database 836 may be loaded onthe media controller 804 at the point of manufacture. Optionally, thelanguage database 836 can be modified, updated, and/or otherwise changedto alter the data stored therein. For instance, additional languages maybe supported by adding the language data to the language database 836.In some cases, this addition of languages can be performed via accessingadministrative functions on the media controller 804 and loading the newlanguage modules via wired (e.g., USB, etc.) or wireless communication.In some cases, the administrative functions may be available via avehicle console device 248, a user device 212, 248, and/or other mobilecomputing device that is authorized to access administrative functions(e.g., based at least partially on the device's address, identification,etc.).

One or more video controllers 840 may be provided for controlling thevideo operation of the devices 212, 248, 882 associated with thevehicle. Optionally, the video controller 840 may include a displaycontroller for controlling the operation of touch sensitive screens,including input (touch sensing) and output (display) functions. Videodata may include data received in a stream and unpacked by a processorand loaded into a display buffer. In this example, the processor andvideo controller 840 can optimize the display based on thecharacteristics of a screen of a display device 212, 248, 882. Thefunctions of a touch screen controller may be incorporated into othercomponents, such as a media processor 808 or display subsystem.

The audio controller 844 can provide control of the audio entertainmentsystem (e.g., radio, subscription music service, multimediaentertainment, etc.), and other audio associated with the vehicle 104(e.g., navigation systems, vehicle comfort systems, convenience systems,etc.). Optionally, the audio controller 844 may be configured totranslate digital signals to analog signals and vice versa. As can beappreciated, the audio controller 844 may include device drivers thatallow the audio controller 844 to communicate with other components ofthe system 800 (e.g., processors 816, 808, audio I/O 874, and the like).

The system 800 may include a profile identification module 848 todetermine whether a user profile is associated with the vehicle 104.Among other things, the profile identification module 848 may receiverequests from a user 216, or device 212, 228, 248, to access a profilestored in a profile database 856 or profile data 252. Additionally oralternatively, the profile identification module 848 may request profileinformation from a user 216 and/or a device 212, 228, 248, to access aprofile stored in a profile database 856 or profile data 252. In anyevent, the profile identification module 848 may be configured tocreate, modify, retrieve, and/or store user profiles in the profiledatabase 856 and/or profile data 252. The profile identification module848 may include rules for profile identification, profile informationretrieval, creation, modification, and/or control of components in thesystem 800.

By way of example, a user 216 may enter the vehicle 104 with a smartphone or other device 212. In response to determining that a user 216 isinside the vehicle 104, the profile identification module 848 maydetermine that a user profile is associated with the user's smart phone212. As another example, the system 800 may receive information about auser 216 (e.g., from a camera 878, microphone 886, etc.), and, inresponse to receiving the user information, the profile identificationmodule 848 may refer to the profile database 856 to determine whetherthe user information matches a user profile stored in the database 856.It is anticipated that the profile identification module 848 maycommunicate with the other components of the system to load one or morepreferences, settings, and/or conditions based on the user profile.Further, the profile identification module 848 may be configured tocontrol components of the system 800 based on user profile information.

Optionally, data storage 852 may be provided. Like the memory 832, thedata storage 852 may comprise a solid state memory device or devices.Alternatively or in addition, the data storage 852 may comprise a harddisk drive or other random access memory. Similar to the data storage852, the profile database 856 may comprise a solid state memory deviceor devices.

An input/output module 860 and associated ports may be included tosupport communications over wired networks or links, for example withother communication devices, server devices, and/or peripheral devices.Examples of an input/output module 860 include an Ethernet port, aUniversal Serial Bus (USB) port, CAN Bus, Institute of Electrical andElectronics Engineers (IEEE) 1594, or other interface. Users may bringtheir own devices (e.g., Bring Your Own Device (BYOD), device 212, etc.)into the vehicle 104 for use with the various systems disclosed.Although most BYOD devices can connect to the vehicle systems (e.g., themedia controller subsystem 348, etc.) via wireless communicationsprotocols (e.g., Wi-Fi™, Bluetooth®, etc.) many devices may require adirect connection via USB, or similar. In any event, the input/outputmodule 860 can provide the necessary connection of one or more devicesto the vehicle systems described herein.

A video input/output interface 864 can be included to receive andtransmit video signals between the various components in the system 800.Optionally, the video input/output interface 864 can operate withcompressed and uncompressed video signals. The video input/outputinterface 864 can support high data rates associated with image capturedevices. Additionally or alternatively, the video input/output interface864 may convert analog video signals to digital signals.

The infotainment system 870 may include information media content and/orentertainment content, informational devices, entertainment devices, andthe associated programming therefor. Optionally, the infotainment system870 may be configured to handle the control of one or more components ofthe system 800 including, but in no way limited to, radio, streamingaudio/video devices, audio devices 880, 882, 886, video devices 878,882, travel devices (e.g., GPS, navigational systems, etc.), wirelesscommunication devices, network devices, and the like. Further, theinfotainment system 870 can provide the functionality associated withother infotainment features as provided herein.

An audio input/output interface 874 can be included to provide analogaudio to an interconnected speaker 880 or other device, and to receiveanalog audio input from a connected microphone 886 or other device. Asan example, the audio input/output interface 874 may comprise anassociated amplifier and analog to digital converter. Alternatively orin addition, the devices 212, 248 can include integrated audioinput/output devices 880, 886 and/or an audio jack for interconnectingan external speaker 880 or microphone 886. For example, an integratedspeaker 880 and an integrated microphone 886 can be provided, to supportnear talk, voice commands, spoken information exchange, and/or speakerphone operations.

Among other things, the system 800 may include devices that are part ofthe vehicle 104 and/or part of a device 212, 248 that is associated withthe vehicle 104. For instance, these devices may be configured tocapture images, display images, capture sound, and present sound.Optionally, the system 800 may include at least one of imagesensors/cameras 878, display devices 882, audio inputdevices/microphones 886, and audio output devices/speakers 880. Thecameras 878 can be included for capturing still and/or video images.Alternatively or in addition, image sensors 878 can include a scanner orcode reader. An image sensor/camera 878 can include or be associatedwith additional elements, such as a flash or other light source. In somecases, the display device 882 may include an audio input device and/oran audio output device in addition to providing video functions. Forinstance, the display device 882 may be a console, monitor, a tabletcomputing device, and/or some other mobile computing device.

FIG. 8B is a block diagram of an embodiment of a user/device interactionsubsystem 817 in a vehicle system 800. The user/device interactionsubsystem 817 may comprise hardware and/or software that conduct variousoperations for or with the vehicle 104. For instance, the user/deviceinteraction subsystem 817 may include at least one user interactionsubsystem 332 and device interaction subsystem 352 as previouslydescribed. These operations may include, but are not limited to,providing information to the user 216, receiving input from the user216, and controlling the functions or operation of the vehicle 104, etc.Among other things, the user/device interaction subsystem 817 mayinclude a computing system operable to conduct the operations asdescribed herein.

Optionally, the user/device interaction subsystem 817 can include one ormore of the components and modules provided herein. For instance, theuser/device interaction subsystem 817 can include one or more of a videoinput/output interface 864, an audio input/output interface 874, asensor module 814, a device interaction module 818, a useridentification module 822, a vehicle control module 826, anenvironmental control module 830, and a gesture control module 834. Theuser/device interaction subsystem 817 may be in communication with otherdevices, modules, and components of the system 800 via thecommunications channel 356.

The user/device interaction subsystem 817 may be configured to receiveinput from a user 216 and/or device via one or more components of thesystem. By way of example, a user 216 may provide input to theuser/device interaction subsystem 817 via wearable devices 802, 806,810, video input (e.g., via at least one image sensor/camera 878, etc.)audio input (e.g., via the microphone, audio input source, etc.),gestures (e.g., via at least one image sensor 878, motion sensor 888,etc.), device input (e.g., via a device 212, 248 associated with theuser, etc.), combinations thereof, and the like.

The wearable devices 802, 806, 810 can include heart rate monitors,blood pressure monitors, glucose monitors, pedometers, movement sensors,wearable computers, and the like. Examples of wearable computers may beworn by a user 216 and configured to measure user activity, determineenergy spent based on the measured activity, track user sleep habits,determine user oxygen levels, monitor heart rate, provide alarmfunctions, and more. It is anticipated that the wearable devices 802,806, 810 can communicate with the user/device interaction subsystem 817via wireless communications channels or direct connection (e.g., wherethe device docks, or connects, with a USB port or similar interface ofthe vehicle 104).

A sensor module 814 may be configured to receive and/or interpret inputprovided by one or more sensors in the vehicle 104. In some cases, thesensors may be associated with one or more user devices (e.g., wearabledevices 802, 806, 810, smart phones 212, mobile computing devices 212,248, and the like). Optionally, the sensors may be associated with thevehicle 104, as described in conjunction with FIGS. 6A-7B.

The device interaction module 818 may communicate with the variousdevices as provided herein. Optionally, the device interaction module818 can provide content, information, data, and/or media associated withthe various subsystems of the vehicle system 800 to one or more devices212, 248, 802, 806, 810, 882, etc. Additionally or alternatively, thedevice interaction module 818 may receive content, information, data,and/or media associated with the various devices provided herein.

The user identification module 822 may be configured to identify a user216 associated with the vehicle 104. The identification may be based onuser profile information that is stored in profile data 252. Forinstance, the user identification module 822 may receive characteristicinformation about a user 216 via a device, a camera, and/or some otherinput. The received characteristics may be compared to data stored inthe profile data 252. Where the characteristics match, the user 216 isidentified. As can be appreciated, where the characteristics do notmatch a user profile, the user identification module 822 may communicatewith other subsystems in the vehicle 104 to obtain and/or record profileinformation about the user 216. This information may be stored in amemory and/or the profile data storage 252.

The vehicle control module 826 may be configured to control settings,features, and/or the functionality of a vehicle 104. In some cases, thevehicle control module 826 can communicate with the vehicle controlsystem 204 to control critical functions (e.g., driving system controls,braking, accelerating, etc.) and/or noncritical functions (e.g., drivingsignals, indicator/hazard lights, mirror controls, window actuation,etc.) based at least partially on user/device input received by theuser/device interaction subsystem 817.

The environmental control module 830 may be configured to controlsettings, features, and/or other conditions associated with theenvironment, especially the interior environment, of a vehicle 104.Optionally, the environmental control module 830 may communicate withthe climate control system (e.g. changing cabin temperatures, fanspeeds, air direction, etc.), oxygen and/or air quality control system(e.g., increase/decrease oxygen in the environment, etc.), interiorlighting (e.g., changing intensity of lighting, color of lighting,etc.), an occupant seating system 648 (e.g., adjusting seat position,firmness, height, etc.), steering wheel 640 (e.g., position adjustment,etc.), infotainment/entertainment system (e.g., adjust volume levels,display intensity adjustment, change content, etc.), and/or othersystems associated with the vehicle environment. Additionally oralternatively, these systems can provide input, set-points, and/orresponses, to the environmental control module 830. As can beappreciated, the environmental control module 830 may control theenvironment based at least partially on user/device input received bythe user/device interaction subsystem 817.

The gesture control module 834 is configured to interpret gesturesprovided by a user 216 in the vehicle 104. Optionally, the gesturecontrol module 834 may provide control signals to one or more of thevehicle systems 300 disclosed herein. For example, a user 216 mayprovide gestures to control the environment, critical and/or noncriticalvehicle functions, the infotainment system, communications, networking,and more. Optionally, gestures may be provided by a user 216 anddetected via one or more of the sensors as described in conjunction withFIGS. 6B-7A. As another example, one or more motion sensors 888 mayreceive gesture input from a user 216 and provide the gesture input tothe gesture control module 834. Continuing this example, the gestureinput is interpreted by the gesture control module 834. Thisinterpretation may include comparing the gesture input to gesturesstored in a memory. The gestures stored in memory may include one ormore functions and/or controls mapped to specific gestures. When a matchis determined between the detected gesture input and the stored gestureinformation, the gesture control module 834 can provide a control signalto any of the systems/subsystems as disclosed herein.

FIG. 8C illustrates a GPS/Navigation subsystem(s) 336. The Navigationsubsystem(s) 336 can be any present or future-built navigation systemthat may use location data, for example, from the Global PositioningSystem (GPS), to provide navigation information or control the vehicle104. The Navigation subsystem(s) 336 can include several components ormodules, such as, one or more of, but not limited to, a GPSAntenna/receiver 892, a location module 896, a maps database 8100, anautomobile controller 8104, a vehicle systems transceiver 8108, atraffic controller 8112, a network traffic transceiver 8116, avehicle-to-vehicle transceiver 8120, a traffic information database8124, etc. Generally, the several components or modules 892-8124 may behardware, software, firmware, computer readable media, or combinationsthereof.

A GPS Antenna/receiver 892 can be any antenna, GPS puck, and/or receivercapable of receiving signals from a GPS satellite or other navigationsystem, as mentioned hereinbefore. The signals may be demodulated,converted, interpreted, etc. by the GPS Antenna/receiver 892 andprovided to the location module 896. Thus, the GPS Antenna/receiver 892may convert the time signals from the GPS system and provide a location(e.g., coordinates on a map) to the location module 896. Alternatively,the location module 896 can interpret the time signals into coordinatesor other location information.

The location module 896 can be the controller of the satellitenavigation system designed for use in automobiles. The location module896 can acquire position data, as from the GPS Antenna/receiver 892, tolocate the user or vehicle 104 on a road in the unit's map database8100. Using the road database 8100, the location module 896 can givedirections to other locations along roads also in the database 8100.When a GPS signal is not available, the location module 896 may applydead reckoning to estimate distance data from sensors 242 including oneor more of, but not limited to, a speed sensor attached to the drivetrain of the vehicle 104, a gyroscope, an accelerometer, etc. GPS signalloss and/or multipath can occur due to urban canyons, tunnels, and otherobstructions. Additionally or alternatively, the location module 896 mayuse known locations of Wi-Fi hotspots, cell tower data, etc. todetermine the position of the vehicle 104, such as by using timedifference of arrival (TDOA) and/or frequency difference of arrival(FDOA) techniques.

The maps database 8100 can include any hardware and/or software to storeinformation about maps, geographical information system information,location information, etc. The maps database 8100 can include any datadefinition or other structure to store the information. Generally, themaps database 8100 can include a road database that may include one ormore vector maps of areas of interest. Street names, street numbers,house numbers, and other information can be encoded as geographiccoordinates so that the user can find some desired destination by streetaddress. Points of interest (waypoints) can also be stored with theirgeographic coordinates. For example, a point of interest may includespeed cameras, fuel stations, public parking, and “parked here” (or “youparked here”) information. The map database contents can be produced orupdated by a server connected through a wireless system in communicationwith the Internet, even as the vehicle 104 is driven along existingstreets, yielding an up-to-date map.

An automobile controller 8104 can be any hardware and/or software thatcan receive instructions from the location module 896 or the trafficcontroller 8112 and operate the vehicle 104. The automobile controller8104 receives this information and data from the sensors 242 to operatethe vehicle 104 without driver input. Thus, the automobile controller8104 can drive the vehicle 104 along a route provided by the locationmodule 896. The route may be adjusted by information sent from thetraffic controller 8112. Discrete and real-time driving can occur withdata from the sensors 242. To operate the vehicle 104, the automobilecontroller 8104 can communicate with a vehicle systems transceiver 8108.

The vehicle systems transceiver 8108 can be any present orfuture-developed device that can comprise a transmitter and/or areceiver, which may be combined and can share common circuitry or asingle housing. The vehicle systems transceiver 8108 may communicate orinstruct one or more of the vehicle control subsystems 328. For example,the vehicle systems transceiver 8108 may send steering commands, asreceived from the automobile controller 8104, to an electronic steeringsystem, to adjust the steering of the vehicle 100 in real time. Theautomobile controller 8104 can determine the effect of the commandsbased on received sensor data 242 and can adjust the commands as needbe. The vehicle systems transceiver 8108 can also communicate with thebraking system, the engine and drive train to speed or slow the car, thesignals (e.g., turn signals and brake lights), the headlights, thewindshield wipers, etc. Any of these communications may occur over thecomponents or function as described in conjunction with FIG. 4.

A traffic controller 8112 can be any hardware and/or software that cancommunicate with an automated traffic system and adjust the function ofthe vehicle 104 based on instructions from the automated traffic system.An automated traffic system is a system that manages the traffic in agiven area. This automated traffic system can instruct cars to drive incertain lanes, instruct cars to raise or lower their speed, instruct acar to change their route of travel, instruct cars to communicate withother cars, etc. To perform these functions, the traffic controller 8112may register the vehicle 104 with the automated traffic system and thenprovide other information including the route of travel. The automatedtraffic system can return registration information and any requiredinstructions. The communications between the automated traffic systemand the traffic controller 8112 may be received and sent through anetwork traffic transceiver 8116.

The network traffic transceiver 8116 can be any present orfuture-developed device that can comprise a transmitter and/or areceiver, which may be combined and can share common circuitry or asingle housing. The network traffic transceiver 8116 may communicatewith the automated traffic system using any known or future-developed,protocol, standard, frequency, bandwidth range, etc. The network traffictransceiver 8116 enables the sending of information between the trafficcontroller 8112 and the automated traffic system.

The traffic controller 8112 can also communicate with another vehicle,which may be in physical proximity (i.e., within range of a wirelesssignal), using the vehicle-to-vehicle transceiver 8120. As with thenetwork traffic transceiver 8116, the vehicle-to-vehicle transceiver8120 can be any present or future-developed device that can comprise atransmitter and/or a receiver, which may be combined and can sharecommon circuitry or a single housing. Generally, the vehicle-to-vehicletransceiver 8120 enables communication between the vehicle 104 and anyother vehicle. These communications allow the vehicle 104 to receivetraffic or safety information, control or be controlled by anothervehicle, establish an alternative communication path to communicate withthe automated traffic system, establish a node including two or morevehicle that can function as a unit, etc. The vehicle-to-vehicletransceiver 8120 may communicate with the other vehicles using any knownor future-developed, protocol standard, frequency, bandwidth range, etc.

The traffic controller 8112 can control functions of the automobilecontroller 8104 and communicate with the location module 896. Thelocation module 896 can provide current location information and routeinformation that the traffic controller 8112 may then provide to theautomated traffic system. The traffic controller 8112 may receive routeadjustments from the automated traffic system that are then sent to thelocation module 896 to change the route. Further, the traffic controller8112 can also send driving instructions to the automobile controller8104 to change the driving characteristics of the vehicle 104. Forexample, the traffic controller 8112 can instruct the automobilecontroller 8104 to accelerate or decelerate to a different speed, changelanes, or perform another driving maneuver. The traffic controller 8112can also manage vehicle-to-vehicle communications and store informationabout the communications or other information in the traffic informationdatabase 8124.

The traffic information database 8124 can be any type of database, suchas relational, hierarchical, object-oriented, and/or the like. Thetraffic information database 8124 may reside on a storage medium localto (and/or resident in) the vehicle control system 204 or in the vehicle104. The traffic information database 8124 may be adapted to store,update, and retrieve information about communications with othervehicles or any active instructions from the automated traffic system.This information may be used by the traffic controller 8112 to instructor adjust the performance of driving maneuvers.

FIG. 9 illustrates an optional communications architecture where, thehost device 908 may include one more routing profiles, permissionmodules, and rules that control how communications within the vehicle104 are to occur. This communications architecture can be used inconjunction with the routing tables, rules and permissions associatedwith access point 456 and optional firewall 484, or can be in lieuthereof. For example, the host device 908 acts as a mobile hot spot toone or more other devices within vehicle 104, such as, other device 1912, other device 2 916, other device 3 920, and other device N 924.Optionally, one or more of the other devices 912 can communicatedirectly with the host device 908 which then provides Internet access tothose devices 912 via the device 908. The host device 908 can act as amobile hot spot for any one or more of the other devices 912, which maynot need to communicate over the network/communications buses 224/404,but could instead connect directly to the host device 908 via, forexample, NFC, Bluetooth®, WiFi, or the like. When the device 908 isacting as the host device, the device 908 can include one or morerouting profiles, permissions, rules modules, and can also act as afirewall for the various inter and intra vehicle communications.

As will be appreciated, there could be alternative host devices, suchas, host 904 which could also act as, for example, a co-host inassociation with device 908. Optionally, one or more of the routingprofile, permission information, and rules could be shared between theco-host devices 904, 908, both of those devices being usable forInternet access for one or more of the other devices, 912-924. As willbe appreciated, the other devices 912-924 need not necessarily connectto one or more of host device 908 and the other device 904 via a directcommunications link, but could also interface with those devices 904,908 utilizing the network/communications buses 224/404 associated withthe vehicle 100. As previously discussed, one or more of the otherdevices can connect to the network/communications buses 224/404utilizing the various networks and/or buses discussed herein which wouldtherefore enable, for example, regulation of the various communicationsbased on the Ethernet zone that the other device 912 is associated with.

An embodiment of one or more modules that may be associated with thevehicle control system 204 may be as shown in FIG. 10. The modules caninclude a communication subsystem interface 1008 in communication withan operating system 1004. The communications may pass through a firewall1044. The firewall 1044 can be any software that can control theincoming and outgoing communications by analyzing the data packets anddetermining whether the packets should be allowed through the firewall,based on applied rule set. A firewall 1044 can establish a “barrier”between a trusted, secure internal network and another network (e.g.,the Internet) that is not assumed to be secure and trusted.

In some situations, the firewall 1044 may establish security zones thatare implemented by running system services and/or applications inrestricted user groups and accounts. A set of configuration files andcallbacks may then be linked to an IP table firewall. The IP tablefirewall can be configured to notify a custom filter application at anyof the layers of the Ethernet packet. The different users/group rightsto access the system may include: system users, which may have exclusiveright over all device firewall rules and running software; a big-brotheruser, which may have access to on board device (OBD) control data andmay be able to communicate with the vehicle subsystem 328 and may beable to alter the parameters in the vehicle control system 204; a dealeruser, which can have rights to read OBD data for diagnostics andrepairs; a dashboard user, which can have rights to launch dashboardapplications and/or authenticate guest users and change theirpermissions to trusted/friend/family, and can read but cannot write intoOBD diagnostic data; a world wide web (WWW) data user, which can haveHTTP rights to respond to HTTP requests (the HTTP requests also cantarget different user data, but may be filtered by default useraccounts); a guest user, which may have no rights; a family/friend user,which may have rights to play media from the media subsystem 348 and/orto stream media to the media subsystem 348.

The operating system 1004 can be a collection of software that managescomputer hardware resources and provides common services forapplications and other programs. The operating system 1004 may scheduletime-sharing for efficient use of the system. For hardware functions,such as input, output, and memory allocation, the operating system 1004can act as an intermediary between applications or programs and thecomputer hardware. Examples of operating systems that may be deployed asoperating system 1004 include Android, BSD, iOS, Linux, OS X, QNX,Microsoft Windows, Windows Phone, IBM z/OS, etc.

The operating system 1004 can include one or more sub-modules. Forexample, a desktop manager 1012 can manage one or more graphical userinterfaces (GUI) in a desktop environment. Desktop GUIs can help theuser to easily access and edit files. A command-line interface (CLI) maybe used if full control over the operating system (OS) 1004 is required.The desktop manager 1012 is described further hereinafter.

A kernel 1028 can be a computer program that manages input/outputrequests from software and translates them into data processinginstructions for the processor 304 and other components of the vehiclecontrol system 204. The kernel 1028 is the fundamental component of theoperating system 1004 that can execute many of the functions associatedwith the OS 1004.

The kernel 1028 can include other software functions, including, but notlimited to, driver(s) 1056, communication software 1052, and/or InternetProtocol software 1048. A driver 1056 can be any computer program thatoperates or controls a particular type of device that is attached to avehicle control system 204. A driver 1056 can communicate with thedevice through the bus 356 or communications subsystem 1008 to which thehardware connects. When a calling program invokes a routine in thedriver 1056, the driver 1056 may issue one or more commands to thedevice. Once the device sends data back to the driver 1056, the driver1056 may invoke routines in the original calling program. Drivers can behardware-dependent and operating-system-specific. Driver(s) 1056 canprovide the interrupt handling required for any necessary asynchronoustime-dependent hardware interface.

The IP module 1048 can conduct any IP addressing, which may include theassignment of IP addresses and associated parameters to host interfaces.The address space may include networks and sub-networks. The IP module1048 can perform the designation of network or routing prefixes and mayconduct IP routing, which transports packets across network boundaries.Thus, the IP module 1048 may perform all functions required for IPmulticast operations.

The communications module 1052 may conduct all functions forcommunicating over other systems or using other protocols not servicedby the IP module 1048. Thus, the communications module 1052 can managemulticast operations over other busses or networks not serviced by theIP module 1048. Further, the communications module 1052 may perform ormanage communications to one or more devices, systems, data stores,services, etc. that are in communication with the vehicle control system204 or other subsystems through the firewall 1044. Thus, thecommunications module 1052 can conduct communications through thecommunication subsystem interface 1008.

A file system 1016 may be any data handling software that can controlhow data is stored and retrieved. The file system 1016 can separate thestored data into individual pieces, and giving each piece a name, caneasily separate and identify the pieces of data. Each piece of data maybe considered a “file”. The file system 1016 can construct datastructure and logic rules used to manage the information and theidentifiers for the information. The structure and logic rules can beconsidered a “file system.”

A device discovery daemon 1020 may be a computer program that runs as abackground process that can discover new devices that connect with thenetwork 356 or communication subsystem 1008 or devices that disconnectfrom the network 356 or communication subsystem 1008. The devicediscovery daemon 1020 can ping the network 356 (the local subnet) whenthe vehicle 104 starts, when a vehicle door opens or closes, or upon theoccurrence of other events. Additionally or alternatively, the devicediscovery daemon 1020 may force Bluetooth®, USB, and/or wirelessdetection. For each device that responds to the ping, the devicediscovery daemon 1020 can populate the system data 208 with deviceinformation and capabilities, using any of one or more protocols,including one or more of, but not limited to, IPv6 Hop-by-Hop Option(HOPOPT), Internet Control Message Protocol (ICMP), Internet GroupManagement Protocol (IGMP), Gateway-to-Gateway Protocol (GGP), InternetProtocol (IP), Internet Stream Protocol (ST), Transmission ControlProtocol (TCP), Exterior Gateway Protocol (EGP), CHAOS, User DatagramProtocol (UDP), etc.

For example, the device discovery daemon 1020 can determine devicecapabilities based on the opened ports the device exposes. If a cameraexposes port 80, then the device discovery daemon 1020 can determinethat the camera is using a Hypertext Transfer Protocol (HTTP).Alternatively, if a device is supporting Universal Plug and Play (UPnP),the system data 208 can include more information, for example, a cameracontrol universal resource locator (URL), a camera zoom URL, etc. When ascan stops, the device discovery daemon 1020 can trigger a dashboardrefresh to ensure the user interface reflects the new devices on thedesktop.

A desktop manager 1012 may be a computer program that manages the userinterface of the vehicle control system 204. The desktop environment maybe designed to be customizable and allow the definition of the desktopconfiguration look-and-feel for a wide range of appliances or devicesfrom computer desktops, mobile devices, computer tablets, etc.Launcher(s), panels, desktop areas, the desktop background,notifications, panes, etc., can be configured from a dashboardconfiguration file managed by the desktop manager 1012. The graphicalelements in which the desktop manager 1012 controls can includelaunchers, the desktop, notification bars, etc.

The desktop may be an area of the display where the applications arerunning. The desktop can have a custom background. Further, the desktopmay be divided into two or more areas. For example, the desktop may bedivided into an upper half of a display and a lower half of the display.Each application can be configured to run in a portion of the desktop.Extended settings can be added to the desktop configuration file, suchthat, some objects may be displayed over the whole desktop or in customsize out of the context of the divided areas.

The notification bar may be a part of a bar display system, which mayprovide notifications by displaying, for example, icons and/or pop-upwindows that may be associated with sound notifications. Thenotification mechanism can be designed for separate plug-ins, which runin separate processes and may subscribe to a system Intelligent InputBus (IBUS)/D-BUS event service. The icons on the notifications bar canbe accompanied with application short-cuts to associated applications,for example, a Bluetooth® manager, a USB manager, radio volume and ortone control, a security firewall, etc.

The desktop manager 1012 may include a windows manager 1032, anapplication launcher 1036, and/or a panel launcher 1040. Each of thesecomponents can control a different aspect of the user interface. Thedesktop manager 1012 can use a root window to create panels that caninclude functionality for one or more of, but not limited to: launchingapplications, managing applications, providing notifications, etc.

The windows manager 1032 may be software that controls the placement andappearance of windows within a graphical user interface presented to theuser. Generally, the windows manager 1032 can provide the desktopenvironment used by the vehicle control system 204. The windows manager1032 can communicate with the kernel 1028 to interface with thegraphical system that provides the user interface(s) and supports thegraphics hardware, pointing devices, keyboard, touch-sensitive screens,etc. The windows manager 1032 may be a tiling window manager (i.e., awindow manager with an organization of the screen into mutuallynon-overlapping frames, as opposed to a coordinate-based stacking ofoverlapping objects (windows) that attempts to fully emulate the desktopmetaphor). The windows manager 1032 may read and store configurationfiles, in the system data 208, which can control the position of theapplication windows at precise positions.

An application manager 1036 can control the function of any applicationover the lifetime of the process. The process or application can belaunched from a panel launcher 1040 or from a remote console. Theapplication manager 1036 can intercept the process name and may takeappropriate action to manage that process. If the process is notrunning, the application manager 1036 can load the process and may bringthe process to a foreground in a display. The application manager 1036may also notify the windows manager 1032 to bring the associatedwindow(s) to a top of a window stack for the display. When a processstarts from a shell or a notification out of the context of the desktop,the application manager 1036 can scan files to match the process namewith the entry name provided. When a match is found, the applicationmanager 1036 can configure the process according to a settings file.

In some situations, the application manager 1036 may restrict anapplication as singleton (i.e., restricts the instantiation of a classto one object). If an application is already running and the applicationmanager 1036 is asked to run the application again, the applicationmanager 1036 can bring the running process to a foreground on a display.There can be a notification event exchange between the windows manager1032 and the application manager 1036 for activating the appropriatewindow for the foreground process. Once an application is launched, theapplication may not be terminated or killed. The application can be sentto the background, except, possibly, for some applications (e.g., mediaplayer, Bluetooth®, notifications, etc.), which may be given a lowestprocess priority.

The panel launcher 1040 can be a widget configured to be placed along aportion of the display. The panel launcher 1040 may be built fromdesktop files from a desktop folder. The desktop folder location can beconfigured by a configuration file stored in system data 208. The panellauncher 1040 can allow for the launching or executing of applicationsor processes by receiving inputs from a user interface to launchprograms.

A desktop plugin 1024 may be a software component that allows forcustomization of the desktop or software interface through theinitiation of plug-in applications.

One or more gestures used to interface with the vehicle control system204 may be as described in conjunction with FIG. 11A through 11K. FIGS.11A through 11H depict various graphical representations of gestureinputs that may be recognized by the devices 212, 248. The gestures maybe performed not only by a user's body part, such as a digit, but alsoby other devices, such as a stylus, that may be sensed by the contactsensing portion(s) of a screen associated with the device 212, 248. Ingeneral, gestures are interpreted differently, based on where thegestures are performed (either directly on a display or in a gesturecapture region). For example, gestures in a display may be directed to adesktop or application, and gestures in a gesture capture region may beinterpreted as for the system.

With reference to FIGS. 11A-11H, a first type of gesture, a touchgesture 1120, is substantially stationary on a portion (e.g., a screen,a display, etc.) of a device 212, 248 for a selected length of time. Acircle 1128 represents a touch or other contact type received atparticular location of a contact sensing portion of the screen. Thecircle 1128 may include a border 1132, the thickness of which indicatesa length of time that the contact is held substantially stationary atthe contact location. For instance, a tap 1120 (or short press) has athinner border 1132A than the border 1132B for a long press 1124 (or fora normal press).

The long press 1124 may involve a contact that remains substantiallystationary on the screen for longer time period than that of a tap 1120.As will be appreciated, differently defined gestures may be registereddepending upon the length of time that the touch remains stationaryprior to contact cessation or movement on the screen.

With reference to FIG. 11C, a drag gesture 1100 on the screen is aninitial contact (represented by circle 1128) with contact movement 1136in a selected direction. The initial contact 1128 may remain stationaryon the screen for a certain amount of time represented by the border1132. The drag gesture typically requires the user to contact an icon,window, or other displayed image at a first location followed bymovement of the contact in a drag direction to a new second locationdesired for the selected displayed image. The contact movement need notbe in a straight line but have any path of movement so long as thecontact is substantially continuous from the first to the secondlocations.

With reference to FIG. 11D, a flick gesture 1104 on the screen is aninitial contact (represented by circle 1128) with truncated contactmovement 1136 (relative to a drag gesture) in a selected direction. Aflick may have a higher exit velocity for the last movement in thegesture compared to the drag gesture. The flick gesture can, forinstance, be a finger snap following initial contact. Compared to a draggesture, a flick gesture generally does not require continual contactwith the screen from the first location of a displayed image to apredetermined second location. The contacted displayed image is moved bythe flick gesture in the direction of the flick gesture to thepredetermined second location. Although both gestures commonly can movea displayed image from a first location to a second location, thetemporal duration and distance of travel of the contact on the screen isgenerally less for a flick than for a drag gesture.

With reference to FIG. 11E, a pinch gesture 1108 on the screen isdepicted. The pinch gesture 1108 may be initiated by a first contact1128A to the screen by, for example, a first digit and a second contact1128B to the screen by, for example, a second digit. The first andsecond contacts 1128A,B may be detected by a common contact sensingportion of a common screen, by different contact sensing portions of acommon screen, or by different contact sensing portions of differentscreens. The first contact 1128A is held for a first amount of time, asrepresented by the border 1132A, and the second contact 1128B is heldfor a second amount of time, as represented by the border 1132B. Thefirst and second amounts of time are generally substantially the same,and the first and second contacts 1128A,B generally occur substantiallysimultaneously. The first and second contacts 1128A,B generally alsoinclude corresponding first and second contact movements 1136A,B,respectively. The first and second contact movements 1136A,B aregenerally in opposing directions. Stated another way, the first contactmovement 1136A is towards the second contact 1136B, and the secondcontact movement 1136B is towards the first contact 1136A. More simplystated, the pinch gesture 1108 may be accomplished by a user's digitstouching the screen in a pinching motion.

With reference to FIG. 11F, a spread gesture 1110 on the screen isdepicted. The spread gesture 1110 may be initiated by a first contact1128A to the screen by, for example, a first digit, and a second contact1128B to the screen by, for example, a second digit. The first andsecond contacts 1128A,B may be detected by a common contact sensingportion of a common screen, by different contact sensing portions of acommon screen, or by different contact sensing portions of differentscreens. The first contact 1128A is held for a first amount of time, asrepresented by the border 1132A, and the second contact 1128B is heldfor a second amount of time, as represented by the border 1132B. Thefirst and second amounts of time are generally substantially the same,and the first and second contacts 1128A,B generally occur substantiallysimultaneously. The first and second contacts 1128A,B generally alsoinclude corresponding first and second contact movements 1136A,B,respectively. The first and second contact movements 1136A,B aregenerally in an opposing direction. Stated another way, the first andsecond contact movements 1136A,B are away from the first and secondcontacts 1128A,B. More simply stated, the spread gesture 1110 may beaccomplished by a user's digits touching the screen in a spreadingmotion.

The above gestures may be combined in any manner, such as those shown byFIGS. 11G and 11H, to produce a determined functional result. Forexample, in FIG. 11G a tap gesture 1120 is combined with a drag or flickgesture 1112 in a direction away from the tap gesture 1120. In FIG. 11H,a tap gesture 1120 is combined with a drag or flick gesture 1116 in adirection towards the tap gesture 1120.

The functional result of receiving a gesture can vary depending on anumber of factors, including a state of the vehicle 104, display, orscreen of a device, a context associated with the gesture, or sensedlocation of the gesture, etc. The state of the vehicle 104 commonlyrefers to one or more of a configuration of the vehicle 104, a displayorientation, and user and other inputs received by the vehicle 104.Context commonly refers to one or more of the particular application(s)selected by the gesture and the portion(s) of the application currentlyexecuting, whether the application is a single- or multi-screenapplication, and whether the application is a multi-screen applicationdisplaying one or more windows. A sensed location of the gesturecommonly refers to whether the sensed set(s) of gesture locationcoordinates are on a touch sensitive display or a gesture capture regionof a device 212, 248, whether the sensed set(s) of gesture locationcoordinates are associated with a common or different display, orscreen, or device 212, 248, and/or what portion of the gesture captureregion contains the sensed set(s) of gesture location coordinates.

A tap, when received by a touch sensitive display of a device 212, 248,can be used, for instance, to select an icon to initiate or terminateexecution of a corresponding application, to maximize or minimize awindow, to reorder windows in a stack, and/or to provide user input suchas by keyboard display or other displayed image. A drag, when receivedby a touch sensitive display of a device 212, 248, can be used, forinstance, to relocate an icon or window to a desired location within adisplay, to reorder a stack on a display, or to span both displays (suchthat the selected window occupies a portion of each displaysimultaneously). A flick, when received by a touch sensitive display ofa device 212, 248 or a gesture capture region, can be used to relocate awindow from a first display to a second display or to span both displays(such that the selected window occupies a portion of each displaysimultaneously). Unlike the drag gesture, however, the flick gesture isgenerally not used to move the displayed image to a specificuser-selected location but to a default location that is notconfigurable by the user.

The pinch gesture, when received by a touch sensitive display or agesture capture region of a device 212, 248, can be used to minimize orotherwise increase the displayed area or size of a window (typicallywhen received entirely by a common display), to switch windows displayedat the top of the stack on each display to the top of the stack of theother display (typically when received by different displays orscreens), or to display an application manager (a “pop-up window” thatdisplays the windows in the stack). The spread gesture, when received bya touch sensitive display or a gesture capture region of a device 212,248, can be used to maximize or otherwise decrease the displayed area orsize of a window, to switch windows displayed at the top of the stack oneach display to the top of the stack of the other display (typicallywhen received by different displays or screens), or to display anapplication manager (typically when received by an off-screen gesturecapture region on the same or different screens).

The combined gestures of FIG. 11G, when received by a common displaycapture region in a common display or screen of a device 212, 248, canbe used to hold a first window location constant for a display receivingthe gesture while reordering a second window location to include awindow in the display receiving the gesture. The combined gestures ofFIG. 11H, when received by different display capture regions in a commondisplay or screen of a device 212, 248 or in different displays orscreens of one more devices 212, 248, can be used to hold a first windowlocation for a display receiving the tap part of the gesture whilereordering a second window location to include a window in the displayreceiving the flick or drag gesture. Although specific gestures andgesture capture regions in the preceding examples have been associatedwith corresponding sets of functional results, it is to be appreciatedthat these associations can be redefined in any manner to producediffering associations between gestures and/or gesture capture regionsand/or functional results.

Gestures that may be completed in three-dimensional space and not on atouch sensitive screen or gesture capture region of a device 212, 248may be as shown in FIGS. 11I-11K. The gestures may be completed in anarea where a sensor, such as an optical sensor, infrared sensor, orother type of sensor, may detect the gesture. For example, the gesture1140 in FIG. 11I may be executed by a person when the person opens theirhand 1164 and moves their hand in a back and forth direction 1148 as agesture 1140 to complete some function with the vehicle 104. For examplegesture 1140 may change the station of the radio in the vehicle 104. Thesensors 242 may both determine the configuration of the hand 1164 andthe vector of the movement. The vector and hand configuration can beinterpreted to mean certain things to the vehicle control system 204 andproduce different results.

In another example of a gesture 1152 in FIG. 11J, a user may configuretheir hand 1164 to extend two fingers and move the hand 1164 in an upand down operation 1156. This gesture 1152 may control the volume of theradio or some other function. For instance, this gesture 1152 may beconfigured to place the vehicle in a “valet” mode to, among otherthings, restrict access to certain features associated with the vehicle.Again, the sensors 242 may determine how the person has configured theirhand 1164, and the vector of the movement. In another example of agesture 1160 shown in FIG. 11K, a user may extend their middle threefingers at an angle that is substantially 45° for vertical from straightvertical and circle the hand in a counter-clockwise motion 1166. Thisgesture 1160 may cause the automobile to change the heat setting or dosome other function. As can be understood by one skilled in the art, theconfigurations of the hand and the types of movement are variable. Thus,the user may configure the hand 1164 in any way imaginable and may alsomove that hand 1164 in any direction with any vector inthree-dimensional space.

The gestures 1140, 1152, 1160, as shown in FIGS. 11I-11K, may occur in apredetermined volume of space within the vehicle 104. For example, asensor may be configured to identify such gestures 1140, 1152, 1160between the front passenger's and front driver's seats over a consolearea within the passenger compartment of the vehicle 104. The gestures1140, 1152, 1160 may be made within area 1 508A between zones A 512A andB 512B. However, there may be other areas 508 where a user may usecertain gestures, where sensors 242 may be able to determine a certainfunction is desired. Gestures that may be similar but used in differentareas within the vehicle 104 may cause different functions to beperformed. For example, the gesture 1140 in FIG. 11I, if used in zone E512E, may change the heat provided in zone E 512E, but may change thestation of a radio if used in zone A 512A and/or zone B 512B. Further,the gestures may be made with other body parts or, for example,different expressions of a person's face and may be used to controlfunctions in the vehicle 104. Also, the user may use two hands in somecircumstances or do other types of physical movements that can causedifferent reactions in the vehicle 104.

FIGS. 12A-12D show various embodiments of a data structure 1200 to storedifferent settings. The data structure 1200 may include one or more ofdata files or data objects 1204, 1250, 1270, 1280. Thus, the datastructure 1200 may represent different types of databases or datastorage, for example, object-oriented data bases, flat file datastructures, relational database, or other types of data storagearrangements. Embodiments of the data structure 1200 disclosed hereinmay be separate, combined, and/or distributed. As indicated in FIGS.12A-12D, there may be more or fewer portions in the data structure 1200,as represented by ellipses 1244. Further, there may be more or fewerfiles in the data structure 1200, as represented by ellipses 1248.

Referring to FIG. 12A, a first data structure is shown. The data file1204 may include several portions 1208-1242 representing different typesof data. Each of these types of data may be associated with a user, asshown in portion 1208.

There may be one or more user records 1240 and associated data storedwithin the data file 1204. As provided herein, the user can be anyperson that uses or rides within the vehicle or conveyance 104. The usermay be identified in portion 1212. For the vehicle 104, the user mayinclude a set of one or more features that may identify the user. Thesefeatures may be the physical characteristics of the person that may beidentified by facial recognition or some other type of system. In othersituations, the user may provide a unique code to the vehicle controlsystem 204 or provide some other type of data that allows the vehiclecontrol system 204 to identify the user. The features or characteristicsof the user are then stored in portion 1212.

Each user, identified in portion 1208, may have a different set ofsettings for each area 508 and/or each zone 512 within the vehicle 104.Thus, each set of settings may also be associated with a predeterminedzone 512 or area 508. The zone 512 is stored in portion 1220, and thearea 508 is stored in portion 1216.

One or more settings may be stored in portion 1224. These settings 1224may be the configurations of different functions within the vehicle 104that are specified by or for that user. For example, the settings 1224may be the position of a seat, the position of a steering wheel, theposition of accelerator and/or brake pedals, positions of mirrors, aheating/cooling setting, a radio setting, a cruise control setting, orsome other type of setting associated with the vehicle 104. Further, invehicles adapted to have a configurable console or a configurable dashor heads-up display, the settings 1224 may also provide for how thatheads-up display, dash, or console are configured for this particularuser.

Each setting 1224 may be associated with a different area 508 or zone512. Thus, there may be more settings 1224 for when the user is thedriver and in zone A 512A, 512A, of area 1, 508A. However, there may besimilar settings 1224 among the different zones 512 or areas 508 asshown in portion 1224. For example, the heating or radio settings forthe user may be similar in every zone 512.

The sensors 242 within the vehicle 104 may be able to either obtain ortrack health data in portion 1228. Health data 1228 may include any typeof physical characteristic associated with the user. For example, aheart rate, a blood pressure, a temperature, or other types of heathdata may be obtained and stored in portion 1228. The user may have thishealth data tracked over a period of time to allow for statisticalanalysis of the user's health while operating the vehicle 104. In thisway, if some function of the user's health deviates from a norm (e.g., abaseline measurement, average measurements taken over time, and thelike), the vehicle 104 may be able to determine there is a problem withthe person and react to that data.

One or more gestures may be stored in portion 1232. Thus, the gesturesused and described in conjunction FIG. 11A through 11K may beconfigurable. These gestures may be determined or created by the userand stored in portion 1132. A user may have different gestures for eachzone 512 or area 508 within the vehicle. The gestures that do certainthings while driving may do other things while in a different area 508of the vehicle 104. Thus, the user may use a first set of gestures whiledriving and a second set while a passenger. Further, one or more usersmay share gestures as shown in portion 1232. Each driver may have acommon set of gestures that they use in zone A 512A, 512A. Each of thesegestures may be determined or captured and then stored with theircharacteristics (e.g., vector, position of gesture, etc.) in portion1232.

One or more sets of safety parameters may be stored in portion 1236.Safety parameters 1236 may be common operating characteristics for thisdriver/passenger or for all drivers/passengers that if deviated from maydetermine there is a problem with the driver/passenger or the vehicle104. For example, a certain route may be taken repeatedly and an averagespeed or mean speed may be determined. If the mean speed deviates bysome number of standard deviations, a problem with the vehicle 104 orthe user may be determined. In another example, the healthcharacteristics or driving experience of the user may be determined. Ifthe user drives in a certain position where their head occupies acertain portion of three-dimensional space within the vehicle 104, thevehicle control system 204 may determine that the safety parameterincludes the users face or head being within this certain portion of thevehicle interior space. If the user's head deviates from that interiorspace for some amount of time, the vehicle control system 204 candetermine that something is wrong with the driver and change thefunction or operation of the vehicle 104 to assist the driver. This mayhappen, for example, when a user falls asleep at the wheel. If theuser's head droops and no longer occupies a certain three dimensionalspace, the vehicle control system 204 can determine that the driver hasfallen asleep and may take control of the operation of the vehicle 204and the automobile controller 8104 may steer the vehicle 204 to the sideof the road. In other examples, if the user's reaction time is too slowor some other safety parameter is not nominal, the vehicle controlsystem 204 may determine that the user is inebriated or having someother medical problem. The vehicle control system 204 may then assumecontrol of the vehicle to ensure that the driver is safe.

Information corresponding to a user and/or a user profile may be storedin the profile information portion 1238. For example, the profileinformation 1238 may include data relating to at least one of currentdata, historical data, a user preference, user habit, user routine,observation, location data (e.g., programmed and/or requesteddestinations, locations of parking, routes traveled, average drivingtime, etc.), social media connections, contacts, brand recognition(e.g., determined via one or more sensors associated with the vehicle104, a device 212, 248, etc.), audible recording data, text data, emaildata, political affiliation, preferred retail locations/sites (e.g.,physical locations, web-based locations, etc.), recent purchases,behavior associated with the aforementioned data, and the like. The datain the profile information portion 1238 may be stored in one or more ofthe data structures 1200 provided herein. As can be appreciated, theseone or more data structures may be stored in one or more memorylocations. Examples of various memory locations are described inconjunction with FIG. 2.

One or more additional data fields may be stored in the linked dataportion 1242 as data and/or locations of data. The linked data 1242 mayinclude at least one of pointers, addresses, location identification,data source information, and other information corresponding toadditional data associated with the data structure 1200. Optionally, thelinked data portion 1242 may refer to data stored outside of aparticular data structure 1200. For example, the linked data portion1242 may include a link/locator to the external data. Continuing thisexample, the link/locator may be resolved (e.g., via one or more of themethods and/or systems provided herein, etc.) to access the data storedoutside of the data structure 1200. Additionally or alternatively, thelinked data portion 1242 may include information configured to link thedata objects 1204 to other data files or data objects 1250, 1270, 1280.For instance, the data object 1204 relating to a user may be linked toat least one of a device data object 1250, a vehicle system data object1270, and a vehicle data object 1280, to name a few.

An embodiment of a data structure 1200 to store information associatedwith one or more devices is shown in FIG. 12B. The data file 1250 mayinclude several portions 1216-1262 representing different types of data.Each of these types of data may be associated with a device, as shown inportion 1252.

There may be one or more device records 1250 and associated data storedwithin the data file 1250. As provided herein, the device may be anydevice that is associated with the vehicle 104. For example, a devicemay be associated with a vehicle 104 when that device is physicallylocated within the interior space 108 of the vehicle 104. As anotherexample, a device may be associated with a vehicle 104 when the deviceregisters with the vehicle 104. Registration may include pairing thedevice with the vehicle 104 and/or one or more of the vehicle systems(e.g., as provided in FIG. 3). In some cases, the registration of adevice with a vehicle 104 may be performed manually and/orautomatically. An example of automatic registration may includedetecting, via one or more of the vehicle systems, that a device isinside the vehicle 104. Upon detecting that the device is inside thevehicle 104, the vehicle system may identify the device and determinewhether the device is or should be registered. Registration may beperformed outside of a vehicle 104 via providing a unique code to thevehicle 104 and/or at least one of the vehicle systems.

The device may be identified in portion 1256. Among other things, thedevice identification may be based on the hardware associated with thedevice (e.g., Media Access Control (MAC) address, Burned-In Address(BIA), Ethernet Hardware Address (EHA), physical address, hardwareaddress, and the like).

Optionally, a device may be associated with one or more users. Forexample, a tablet and/or graphical user interface (GUI) associated withthe vehicle 104 may be used by multiple members of a family. Forinstance, the GUI may be located in a particular area 508 and/or zone512 of the vehicle 104. Continuing this example, when a family member islocated in the particular area 508 and/or zone 512, the device mayinclude various settings, features, priorities, capabilities, and thelike, based on an identification of the family member. The user may beidentified in portion 1254. For the device, the user identificationportion 1254 may include a set of one or more features that may identifya particular user. These features may be the physical characteristics ofthe person that may be identified by facial recognition, or some othertype of system, associated with the device and/or the vehicle 104.Optionally, the user may provide a unique code to the device, or providesome other type of data, that allows the device to identify the user.The features or characteristics of the user are then stored in portion1254.

Each device identified in the device identification portion 1256 mayhave a different set of settings for each area 508 and/or each zone 512,and/or each user of the device. Thus, each set of settings may also beassociated with a predetermined zone 512, area 508, and/or user. Thezone 512 is stored in portion 1220 and the area 508 is stored in portion1216.

One or more settings may be stored in portion 1224. These settings 1224may be similar and/or identical to those previously described. Further,the settings 1224 may also provide for how a device is configured for aparticular user. Each setting 1224 may be associated with a differentarea 508 or zone 512. Thus, there may be more restrictive settings 1224(e.g., restricted multimedia, texting, limited access to devicefunctions, and the like) for the device when the user is the driver andin zone A 512A, 512A, of area 1, 508A. However, when the user is inanother zone 512 or area 508, for example, where the user is notoperating a vehicle 104, the settings 1224 may provide unrestrictedaccess to one or more features of the device (e.g., allowing texting,multimedia, etc.).

Optionally, the capabilities of a device may be stored in portion 1258.Examples of device capabilities may include, but are not limited to, acommunications ability (e.g., via wireless network, EDGE, 3G, 4G, LTE,wired, Bluetooth®, Near Field Communications (NFC), Infrared (IR),etc.), hardware associated with the device (e.g., cameras, gyroscopes,accelerometers, touch interface, processor, memory, display, etc.),software (e.g., installed, available, revision, release date, etc.),firmware (e.g., type, revision, etc.), operating system, system status,and the like. Optionally, the various capabilities associated with adevice may be controlled by one or more of the vehicle systems providedherein. Among other things, this control allows the vehicle 104 toleverage the power and features of various devices to collect, transmit,and/or receive data.

One or more priorities may be stored in portion 1260. The priority maycorrespond to a value, or combination of values, configured to determinehow a device interacts with the vehicle 104 and/or its various systems.The priority may be based on a location of the device (e.g., as storedin portions 1216, 1220). A default priority can be associated with eacharea 508 and/or zone 512 of a vehicle 104. For example, the defaultpriority associated with a device found in zone 1 512A of area 1 508A(e.g., a vehicle operator position) may be set higher than an (or thehighest of any) alternative zone 512 or area 508 of the vehicle 104.Continuing this example, the vehicle 104 may determine that, althoughother devices are found in the vehicle, the device, having the highestpriority, controls features associated with the vehicle 104. Thesefeatures may include vehicle control features, critical and/ornon-critical systems, communications, and the like. Additionally oralternatively, the priority may be based on a particular user associatedwith the device. Optionally, the priority may be used to determine whichdevice will control a particular signal in the event of a conflict.

Registration data may be stored in portion 1262. As described above,when a particular device registers with a vehicle 104, data related tothe registration may be stored in the registration data portion 1262.Such data may include, but is not limited to, registration information,registration codes, initial registration time, expiration ofregistration, registration timers, and the like. Optionally, one or moresystems of the vehicle 104 may refer to the registration data portion1262 to determine whether a device has been previously registered withthe vehicle 104. As shown in FIG. 12B, User 4 of Device 2 has not beenregistered. In this case, the registration data field 1262, for thisuser, may be empty, contain a null value, or otherinformation/indication that there is no current registration informationassociated with the user.

Additionally or alternatively, the data structure 1200 may include aprofile information portion 1238 and/or a linked data portion 1242.Although the profile information portion 1238 and/or the linked dataportion 1242 may include different information from that describedabove, it should be appreciated that the portions 1238, 1242 may besimilar, or identical, to those as previously disclosed.

An embodiment of a data structure 1200 to store information associatedwith one or more vehicle systems is shown in FIG. 12C. The data file1270 may include several portions 1216-1279 representing different typesof data. Each of these types of data may be associated with a vehiclesystem, as shown in portion 1272.

There may be one or more system records 1270 and associated data storedwithin the data file 1270. As provided herein, the vehicle systems maybe any system and/or subsystem that is associated with the vehicle 104.Examples of various systems are described in conjunction with FIG. 3 andother related Figs. (e.g., systems 324-352, etc.). One example of asystem associated with the vehicle 104 is the vehicle control system204. Other systems may include communications subsystems 344, vehiclesubsystems 328, and media subsystems 348, to name a few. It should beappreciated that the various systems may be associated with the interiorspace 108 and/or the exterior of the vehicle 104.

Each system may include one or more components. The components may beidentified in portion 1274. Identification of the one or more componentsmay be based on hardware associated with the component. Thisidentification may include hardware addresses similar to those describedin conjunction with the devices of FIG. 12B. Additionally oralternatively, a component can be identified by one or more signals sentvia the component. Such signals may include an Internet Protocol (IP),or similar, address as part of the signal. Optionally, the signal mayidentify the component sending the signal via one or more of a header, afooter, a payload, and/or an identifier associated with the signal(e.g., a packet of a signal, etc.).

Each system and/or component may include priority type information inportion 1276. Among other things, the priority type information storedin portion 1276 may be used by the various methods and systems providedherein to differentiate between critical and non-critical systems.Non-limiting examples of critical systems may correspond to thosesystems used to control the vehicle 104, such as, steering control,engine control, throttle control, braking control, and/or navigationinformational control (e.g., speed measurement, fuel measurement, etc.)Non-critical systems may include other systems that are not directlyrelated to the control of the vehicle 104. By way of example,non-critical systems may include media presentation, wirelesscommunications, comfort settings systems (e.g., climate control, seatposition, seat warmers, etc.), and the like. Although examples ofcritical and/or non-critical systems are provided above, it should beappreciated that the priority type of a system may change (e.g., fromcritical to non-critical, from non-critical to critical, etc.) dependingon the scenario. For instance, although the interior climate controlsystem may be classified as a non-critical system at a first point intime, it may be subsequently classified as a critical system when atemperature inside/outside of the vehicle 104 is measured at a dangerouslevel (e.g., sub-zero Fahrenheit, greater than 90-degrees Fahrenheit,etc.). As such, the priority type may be associated with temperatureconditions, air quality, times of the day, condition of the vehicle 104,and the like.

Each system may be associated with a particular area 508 and/or zone 512of a vehicle 104. Among other things, the location of a system may beused to assess a state of the system and/or provide how the systeminteracts with one or more users of the vehicle 104. As can beappreciated each system may have a different set of settings for eacharea 508 and/or each zone 512, and/or each user of the system. Thus,each set of settings may also be associated with a predetermined zone512, area 508, system, and/or user. The zone 512 is stored in portion1220 and the area 508 is stored in portion 1216.

One or more settings may be stored in portion 1224. These settings 1224may be similar and/or identical to those previously described. Further,the settings 1224 may also provide for how a system is configured for aparticular user. Each setting 1224 may be associated with a differentarea 508 or zone 512. For instance, a climate control system may beassociated with more than one area 508 and/or zone 512. As such, a firstuser seated in zone 1 512A of area 1 508A may store settings related tothe climate control of that zone 512A that are different from otherusers and/or zones 512 of the vehicle 104. Optionally, the settings maynot be dependent on a user. For instance, specific areas 508 and/orzones 512 of a vehicle 104 may include different, default, or the samesettings based on the information stored in portion 1224.

The various systems and/or components may be able to obtain or trackhealth status data of the systems and/or components in portion 1278. Thehealth status 1278 may include any type of information related to astate of the systems. For instance, an operational condition,manufacturing date, update status, revision information, time inoperation, fault status, state of damage detected, inaccurate datareporting, and other types of component/system health status data may beobtained and stored in portion 1278.

Each component and/or system may be configured to communicate withusers, systems, servers, vehicles, third parties, and/or other endpointsvia one or more communication type. At least one communication abilityand/or type associated with a system may be stored in the communicationtype portion 1279. Optionally, the communication types contained in thisportion 1279 may be ordered in a preferential order of communicationtypes. For instance, a system may be configured to preferablycommunicate via a wired communication protocol over one or more wiredcommunication channels (e.g., due to information transfer speeds,reliability, and the like). However, in this instance, if the one ormore wired communication channels fail, the system may transferinformation via an alternative communication protocol and channel (e.g.,a wireless communication protocol and wireless communication channel,etc.). Among other things, the methods and systems provided herein maytake advantage of the information stored in the communication typeportion 1279 to open available communication channels in the event of acommunication channel failure, listen on other ports for informationtransmitted from the systems, provide a reliability rating based on thenumber of redundant communication types for each component, and more.Optionally, a component or system may be restricted from communicatingvia a particular communication type (e.g., based on rules, traffic,critical/non-critical priority type, and the like). In this example, thecomponent or system may be forced by the vehicle control system 204 touse an alternate communication type where available, ceasecommunications, or store communications for later transfer.

Additionally or alternatively, the data structure 1200 may include aprofile information portion 1238 and/or a linked data portion 1242.Although the profile information portion 1238 and/or the linked dataportion 1242 may include different information from that describedabove, it should be appreciated that the portions 1238, 1242 may besimilar, or identical, to those as previously disclosed.

Referring now to FIG. 12D, a data structure 1200 is shown optionally.The data file 1280 may include several portions 1216-1286 representingdifferent types of data. Each of these types of data may be associatedwith a vehicle, as shown in portion 1282.

There may be one or more vehicle records 1280 and associated data storedwithin the data file 1282. As provided herein, the vehicle 104 can beany vehicle or conveyance 104 as provided herein. The vehicle 104 may beidentified in portion 1282. Additionally or alternatively, the vehicle104 may be identified by one or more systems and/or subsystems. Thevarious systems of a vehicle 104 may be identified in portion 1284. Forexample, various features or characteristics of the vehicle 104 and/orits systems may be stored in portion 1284. Optionally, the vehicle 104may be identified via a unique code or some other type of data thatallows the vehicle 104 to be identified.

Each system may be associated with a particular area 508 and/or zone 512of a vehicle 104. Among other things, the location of a system may beused to assess a state of the system and/or provide how the systeminteracts with one or more users of the vehicle 104. As can beappreciated each system may have a different set of settings for eacharea 508 and/or each zone 512, and/or each user of the system. Thus,each set of settings may also be associated with a predetermined zone512, area 508, system, and/or user. The zone 512 is stored in portion1220 and the area 508 is stored in portion 1216.

One or more settings may be stored in portion 1224. These settings 1224may be similar and/or identical to those previously described. Further,the settings 1224 may also provide for how a vehicle and/or its systemsare configured for one or more users. Each setting 1224 may beassociated with a different area 508 or zone 512. Optionally, thesettings may not be dependent on a particular user. For instance,specific areas 508 and/or zones 512 of a vehicle 104 may includedifferent, default, or the same settings based on the information storedin portion 1224.

The various systems and/or components may be able to obtain or trackhealth status data of the systems and/or components in portion 1278. Thehealth status 1278 may include any type of information related to astate of the systems. For instance, an operational condition,manufacturing date, update status, revision information, time inoperation, fault status, state of damage detected, inaccurate datareporting, and other types of component/system health status data may beobtained and stored in portion 1278.

One or more warnings may be stored in portion 1286. The warnings data1286 may include warning generated by the vehicle 104, systems of thevehicle 104, manufacturer of the vehicle, federal agency, third party,and/or a user associated with the vehicle. For example, severalcomponents of the vehicle may provide health status information (e.g.,stored in portion 1278) that, when considered together, may suggest thatthe vehicle 104 has suffered some type of damage and/or failure.Recognition of this damage and/or failure may be stored in the warningsdata portion 1286. The data in portion 1286 may be communicated to oneor more parties (e.g., a manufacturer, maintenance facility, user,etc.). In another example, a manufacturer may issue a recallnotification for a specific vehicle 104, system of a vehicle 104, and/ora component of a vehicle 104. It is anticipated that the recallnotification may be stored in the warning data field 1286. Continuingthis example, the recall notification may then be communicated to theuser of the vehicle 104 notifying the user of the recall issued by themanufacturer.

Additionally or alternatively, the data structure 1200 may include aprofile information portion 1238 and/or a linked data portion 1242.Although the profile information portion 1238 and/or the linked dataportion 1242 may include different information from that describedabove, it should be appreciated that the portions 1238, 1242 may besimilar, or identical, to those as previously disclosed.

An embodiment of a method 1300 for storing settings for a user 216associated with vehicle 104 is shown in FIG. 13. While a general orderfor the steps of the method 1300 is shown in FIG. 13, the method 1300can include more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 13. Generally, the method 1300starts with a start operation 1304 and ends with an end operation 1336.The method 1300 can be executed as a set of computer-executableinstructions executed by a computer system and encoded or stored on acomputer readable medium. Hereinafter, the method 1300 shall beexplained with reference to the systems, components, modules, software,data structures, user interfaces, etc. described in conjunction withFIGS. 1-12.

A person may enter the vehicle space 108. One or more sensors 242 maythen identify that a person is sitting within the vehicle 104, in step1308. For example, sensors 242 in a seat, may determine that some newamount of weight has been registered. The amount of weight may fallwithin predetermined parameters (e.g., over a threshold, in a specificrange, etc.). This weight may then be determined to be a person by oneor more optical or other sensors 242. The vehicle control system 204 maythen determine that a person is in a certain zone 512 or area 508. Forexample, the sensors 242 may send signals to the vehicle controls system204 that an event has occurred. This information may be sent to thevehicle control system processor 304 to determine the zone 512 and area508 where the event occurred. Further, the vehicle control system 204may then identify the person, in step 1312.

The vehicle control system 204 can receive the information from thesensors 242 and use that information to search the database 1200 thatmay be stored within the system data 208. The sensor data may becompared to ID characteristics 1212 to determine if the person hasalready been identified. The vehicle control system 204 may also sendthe characteristic data from the sensors to the communication network224 to a server 228 to compare the sensor data to stored data 232 thatmay be stored in a cloud system. The person's features can be comparedto stored features 1212 to determine if the person in the vehicle 104can be identified.

If the person has been identified previously and their characteristicsstored in portion 1212, the method 1300 proceeds YES to step 1316 wherethat person may be identified. In identifying a person, the informationassociated with that person 1240 may be retrieved and provided to thevehicle control system 204 for further action. If a person cannot beidentified by finding their sensor characteristics in portion 1212, themethod 1300 proceeds NO to step 1320. In step 1320, the vehicle controlsystem 204, using an application, may create a new record in table 1200for the user. This new record may store a user identifier and theircharacteristics 1212. It may also store the area 508 and zone 512 indata portions 1216 and 1220. The new record may then be capable ofreceiving new settings data for this particular user. In this way, thevehicle 104 can automatically identify or characterize a person so thatsettings may be established for the person in the vehicle 104.

The input module 312 may then determine if settings are to be stored, instep 1324. Settings might be any configuration of the vehicle 104 thatmay be associated with the user. The determination may be made afterreceiving a user input from the user. For example, the user may make aselection on a touch sensitive display indicating that settingscurrently made are to be stored. In other situations, a period of timemay elapse after the user has made a configuration. After determiningthat the user is finished making changes to the settings, based on thelength of the period of time since the setting was established, thevehicle control system 204 can save the setting. Thus, the vehiclecontrol system 204 can make settings automatically based on reaching asteady state for settings for user.

The vehicle control system 204 may then store the settings for theperson, in step 1328. The user interaction subsystem 332 can make a newentry for the user 1208 in data structure 1204. The new entry may beeither a new user or a new settings listed in 1224. The settings may bestored based on the area 508 and zone 512. As explained previously, thesettings can be any kind of configuration of the vehicle 104 that may beassociated with the user in that area 508 and the zone 512.

The settings may also be stored in cloud storage, in step 1332. Thus,the vehicle control system 204 can send the new settings to the server228 to be stored in storage 232. In this way, these new settings may beported to other vehicles for the user. Further, the settings in storagesystem 232 may be retrieved, if local storage does not include thesettings in storage system 208.

Additionally or alternatively, the settings may be stored in profiledata 252. As provided herein, the profile data 252 may be associatedwith one or more devices 212, 248, servers 228, vehicle control systems204, and the like. Optionally, the settings in profile data 252 may beretrieved in response to conditions. For instance, the settings may beretrieved from at least one source having the profile data if localstorage does not include the settings in storage system 208. As anotherexample, a user 216 may wish to transfer settings stored in profile data252 to the system data 208. In any event, the retrieval and transfer ofsettings may be performed automatically via one or more devices 204,212, 248, associated with the vehicle 104.

An embodiment of a method 1400 to configure the vehicle 104 based onstored settings is shown in FIG. 14. A general order for the steps ofthe method 1400 is shown in FIG. 14. Generally, the method 1400 startswith a start operation 1404 and ends with an end operation 1428. Themethod 1400 can include more or fewer steps or can arrange the order ofthe steps differently than those shown in FIG. 14. The method 1400 canbe executed as a set of computer-executable instructions executed by acomputer system and encoded or stored on a computer readable medium.Hereinafter, the method 1400 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-13.

The vehicle control system 204 can determine if a person is in a zone512 or area 508, in step 1408. This determination may be made byreceiving data from one or more sensors 242. The vehicle 104 can usefacial recognition, weight sensors, heat sensors, or other sensors todetermine whether a person is occupying a certain zone 512.

Using the information from the sensors 242, the vehicle control system204 can identify the person, in step 1412. The vehicle control system204 can obtain characteristics for the user currently occupying the zone512 and compare those characteristics to the identifying features inportion 1212 of data structure 1204. Thus, the settings in portion 1224may be retrieved by identifying the correct zone 512, area 508, andcharacteristics for the user.

The vehicle control system 204 can first determine if there are settingsassociated with the identified person for that zone 512 and/or area 508,in step 1416. After identifying the user by matching characteristicswith the features in portion 1212, the vehicle control system 204 candetermine if there are settings for the user for the area 1216 and zone1220 the user currently occupies. If there are settings, then thevehicle control system 204 can make the determination that there aresettings in portion 1224, and the vehicle control system 204 may thenread and retrieve those settings, in step 1420. The settings may be thenused to configure or react to the presence of the user, in step 1424.Thus, these settings may be obtained to change the configuration of thevehicle 104, for example, how the position of the seats or mirrors areset, how the dash, console, or heads up display is configured, how theheat or cooling is configured, how the radio is configured, or how otherdifferent configurations are made.

Embodiments of a method 1500 for storing settings in cloud storage areshown in FIG. 15. A general order for the steps of the method 1500 isshown in FIG. 15. Generally, the method 1500 starts with a startoperation 1504 and ends with an end operation 1540. The method 1500 caninclude more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 15. The method 1500 can be executedas a set of computer-executable instructions executed by a computersystem and encoded or stored on a computer readable medium. Hereinafter,the method 1500 shall be explained with reference to the systems,components, modules, software, data structures, user interfaces, etc.described in conjunction with FIGS. 1-14.

The vehicle control system 204 can determine if a person is in a zone512 or area 508, in step 1508. As explained previously, the vehiclecontrol system 204 can receive vehicle sensor data from vehicle sensors242 that show a person has occupied a zone 512 or an area 508 of thevehicle 104. Using the vehicle sensor data, the vehicle control system204 can determine characteristics of the person, in step 1512. Thesecharacteristics are compared to the features in portion 1212 of the datastructure 1204. From this comparison, the vehicle control system 204 candetermine if the person is identified within the data structure 1204, instep 1516. If there is a comparison and the person can be identified,the method 1500 proceeds YES to step 1520. However, if the person cannotbe identified, the method 1500 proceeds NO, to step 1524.

In step 1520, the person is identified in portion 1208 by the successfulcomparison of the characteristics and the features. It should be notedthat there may be a degree of variability between the characteristicsand the features in portion 1212. Thus, the comparison may not be anexact comparison but may use methods known in the art to make astatistically significant comparison between the characteristicsreceived from the sensors 242 and the features stored in portion 1212.In step 1524, the characteristics received from sensors 242 are used tocharacterize the person. In this way, the received characteristics maybe used as an ID, in portion 1212, for a new entry for a new user inportion 1208.

The user may make one or more settings for the vehicle 104. The vehiclecontrol system 204 may determine if the settings are to be stored, instep 1528. If the settings are to be stored, the method 1500 proceedsYES to step 1536. If the settings are not to be stored or if there areno settings to be stored, the method 1500 proceeds NO to step 1532. Instep 1532, the vehicle control system 204 can retrieve the settings inthe portion 1224 of the data structure 1204. Retrieval of the settingsmay be as described in conjunction with FIG. 14. If settings are to bestored, the vehicle control system 204 can send those settings to server228 to be stored in data storage 232, in step 1536. Data storage 232acts as cloud storage that can be used to retrieve information on thesettings from other vehicles or from other sources. Thus, the cloudstorage 232 allows for permanent and more robust storage of userpreferences for the settings of the vehicle 104.

An embodiment of a method 1600 for storing gestures associated with theuser is shown in FIG. 16. A general order for the steps of the method1600 is shown in FIG. 16. Generally, the method 1600 starts with a startoperation 1604 and ends with an end operation 1640. The method 1600 caninclude more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 16. The method 1600 can be executedas a set of computer-executable instructions executed by a computersystem and encoded or stored on a computer readable medium. Hereinafter,the method 1600 shall be explained with reference to the systems,components, modules, software, data structures, user interfaces, etc.described in conjunction with FIGS. 1-15.

Vehicle control system 204 may receive sensor data from sensors 242 todetermine a person is occupying a zone 512 in an area 508 of the vehicle104, in step 1608. The sensor data may provide characteristics for theperson, in step 1612. The vehicle control system 204 may then use thecharacteristics to determine if the person can be identified, in step1616. The vehicle control system 204 may compare the characteristics tothe features in portion 1212 for the people having been recognized andhaving data associated therewith. If a comparison is made between thecharacteristics and the features in portion 1212, the person can beidentified, and the method 1600 proceeds YES to step 1620. If there isno comparison, the method 1600 may proceed NO to step 1624. In step1620, the person may be identified by the vehicle control system 204.Thus, the person's features and associated data record 1240 may bedetermined and the user identified in portion 1208. If the person is notidentified, the vehicle control system 204 can characterize the personin step 1624 by establishing a new record in data structure 1204 usingthe characteristics, received from the sensors 242, for the features inportion 1212.

Thereinafter, the vehicle control system 204 may determine if gesturesare to be stored and associated with the user, in step 1628. The vehiclecontrol system 204 may receive user input on a touch sensitive displayor some other type of gesture capture region which acknowledges that theuser wishes to store one or more gestures. Thus, the user may createtheir own gestures such as those described in conjunction with FIGS.11A-11K. These gestures may then be characterized and stored in datastructure 1204. If there are gestures to be stored, the method 1600proceeds YES to step 1636. If gestures are not to be stored the method1600 may proceed NO to step 1632.

In step 1632, the vehicle control system 204 can retrieve currentgestures from portion 1232, which are associated with user 1240. Thesegestures may be used then to configure how the vehicle 104 will react ifa gesture is received. If gestures are to be stored, the vehicle controlsystem 204 may store characteristics, in step 1636, as received fromsensor 242 or from one more user interface inputs. These characteristicsmay then be used to create the stored gestures 1232, in data structure1204. The characteristics may include what the gesture looks like orappears and also what affect the gesture should have. This informationmay then be used to change the configuration or operation of the vehicle104 based on the gesture if it is received at a later time.

An embodiment of a method 1700 for receiving a gesture and configuringthe vehicle 104 based on the gesture may be as provided in FIG. 17. Ageneral order for the steps of the method 1700 is shown in FIG. 17.Generally, the method 1700 starts with a start operation 1704 and endswith an end operation 1728. The method 1700 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 17. The method 1700 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method1700 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-16.

A vehicle control system 204 can receive sensor data from vehiclesensors 242. The vehicle sensor data can be used by the vehicle controlsystem 204 to determine that a person is in a zone 512 or area 508, instep 1708. The vehicle sensor data may then be used to compare againstfeature characteristics 1212 to identify a person, in step 1712. Thevehicle control system 204 thereinafter may receive a gesture, in step1716. The gesture may be perceived by vehicle sensors 242 or received ina gesture capture region. The gesture may be as described in conjunctionwith FIGS. 11A-11K. Upon receiving the gesture, the vehicle controlsystem 204 can compare the gesture to gesture characteristics in portion1232, in step 1720. The comparison may be made so that a statisticallysignificant correlation between the sensor data or gesture data and thegesture characteristic 1232 is made. Upon identifying the gesture, thevehicle control system 204 can configure the vehicle 104 and/or react tothe gesture, in step 1724. The configuration or reaction to the gesturemay be as prescribed in the gesture characteristic 1232.

An embodiment of a method 1800 for storing health data may be as shownin FIG. 18. A general order for the steps of the method 1800 is shown inFIG. 18. Generally, the method 1800 starts with a start operation 1804and ends with an end operation 1844. The method 1800 can include more orfewer steps or can arrange the order of the steps differently than thoseshown in FIG. 18. The method 1800 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method1800 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-17.

Vehicle control system 204 can receive sensor data from sensors 242. Thesensor data may be used to determine that a person is in a zone 512 orarea 508, in step 1808. The sensor data may then be used to determinecharacteristics of the person, in step 1812. From the characteristics,the vehicle control system 204 can determine if a person may beidentified in data structure 1204, in step 1816. If it is determinedthat the person can be identified in step 1816, the method 1800 proceedsYES to step 1820. If the person cannot be identified, the method 1800proceeds NO to step 1824. A person may be identified by matching thecharacteristics of a person from the sensor data to the features shownin portion 1212. If these comparisons are statistically significant, theperson may be identified in portion 1208, in step 1820. However, if theperson is not identified in portion 1208, the vehicle control system 204can characterize the person using the vehicle sensor data, in step 1824.In this way, the vehicle control system 204 can create a new record fora new user in data structure 1204.

Thereinafter, the vehicle control system 204 may receive health and/orsafety data from the vehicle sensors 242, in step 1828. The vehiclecontrol system 204 can determine if the health or safety data is to bestored, in step 1832. The determination is made as to whether or notthere is sufficient health data or safety parameters, in portion 1228and 1236, to provide a reasonable baseline data pattern for the user1240. If there is data to be received and stored, the vehicle controlsystem 204 can store the data for the person in portions 1228 and 1236of the data structure 1204, in step 1832.

The vehicle control system 204 may then wait a period of time, in step1836. The period of time may be any amount of time from seconds tominutes to days. Thereinafter, the vehicle control system 204 canreceive new data from vehicle sensors 242, in step 1828. Thus, thevehicle control system 204 can receive data periodically and update orcontinue to refine the health data and safety parameters in datastructure 1204. Thereinafter, the vehicle control system 204 mayoptionally store the health and safety data in cloud storage 232 bysending it through the communication network 224 to the server 228, instep 1840.

An embodiment of a method 1900 for monitoring the health of a user maybe as shown in FIG. 19. A general order for the steps of the method 1900is shown in FIG. 19. Generally, the method 1900 starts with a startoperation 1904 and ends with an end operation 1928. The method 1900 caninclude more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 19. The method 1900 can be executedas a set of computer-executable instructions executed by a computersystem and encoded or stored on a computer readable medium. Hereinafter,the method 1900 shall be explained with reference to the systems,components, modules, software, data structures, user interfaces, etc.described in conjunction with FIGS. 1-18.

The vehicle control system 204 can receive health data from sensors 242.The health data may be received in step 1908. The vehicle control system204 may then compare the received health data to stored healthparameters in portion 1228 or portion 1236, in step 1912. The comparisonmay check if there is statistically significant separation ordisagreement between the received health data and the stored healthdata. Thus, the vehicle control system 204 can make a health comparisonof the user based on a baseline of health data previously stored. Astatistically significant comparison may include determining if thereare any parameters more than three standard deviations from the averageor norm, any parameter that is increasing or decreasing over a period ofeight different measurements, a measurement that is more than twostandard deviations from the norm more than three measurementsconsecutively, or other types of statistical comparisons.

If the vehicle control system 204 determines that measured healthparameter does deviate from the norm, the vehicle control system 204 candetermine whether the health data is within acceptable limits, in step1916. If the health data is within acceptable limits, the method 1900proceeds YES back to receiving new health data, in step 1908. In thisway, the health data is periodically or continually monitored to ensurethat the driver is in a healthy state and able to operate the vehicle.If the health data is not within acceptable parameters, the method 1900may proceed NO to step 1924 where the vehicle control system 204 mayreact to the change in the health data. The reaction may include anymeasure to provide for the safety of the user, such as stopping thevehicle, beginning to drive the vehicle, driving the vehicle to a newlocation, such as a hospital, waking the driver with an alarm or othernoise, or performing some other function that may help maintain thehealth or safety of the user.

The health data received may be a reaction from the driver. For example,the driver may call for help or ask the vehicle for assistance. Forexample, the driver or passenger may say that they are having a medicalemergency and ask the car to perform some function to help. The functionto help may include driving the person to a hospital or stopping the carand calling for emergency assistance.

An embodiment of a gesture control module 834 is shown in FIG. 20. Thegesture control module 834 may be hardware, software, or a combinationof hardware and software. In one situation, the gesture control module834 may be part of the user and device interaction subsystem 352, whichis described in conjunction with FIGS. 3 and 8B. In other situations,the gesture control module 834 may be a desktop plug-in 1024, asdescribed in conjunction with FIG. 10.

The gesture control module 834 can include one or more modules. Themodule may include one or more of, but are not limited to, an originmodule 2008, a focus module 2012, a user customization module 2016, avoice control module 2020, a verification module 2024, and/or a gesturerecognition module 2004. Each of these different modules may bedescribed hereinafter. It should be noted that the modules 2004 through2024 appear to be included with the gesture control module 834, but maybe separate functions embodied in another part of the vehicle control204.

The origin module 2008 is generally operable to determine the origin ofa gesture. The origin of the gesture may be the same as the location ofthe person providing the gesture, or may be a different zone 512, adifferent area 508, a different location within a zone 512 or area 508,or on a console 248 that is near the person. Generally, the originmodule 2008 receives vehicle sensor data from one or more vehiclesensors 242. The vehicle sensors 242 may be as described in conjunctionwith FIG. 2 and FIGS. 6A through 7B. Based on which sensors provideinformation, the origin module 2008 can identify and determine where thegesture is provided. For example, if two sensors, within a first zone512A, determine that a gesture has been made, the origin module 2008 maybe able to determine that the gesture originates in zone A 512A. It maybe possible for the origin module 2008 to determine a location of thegesture within a zone 512 or area 508. Thus, beyond just determiningthat the gesture happened within the more general zone 512 or area 508,the origin module 2008 can determine that the gesture occurred within aparticular quadrant or portion of a zone 512 or area 508.

The origin module 2008 may also determine that the gesture occurred in azone 512 or area 508 that is different from where a person making thegesture is located. For example, if the origin module 2008 determinesthat a gesture occurred within zone B 512B, but no occupant currently isoccupying that zone 512B, the origin module 2008 can determine that thegesture originated in a zone 512 separate from zone A 512A in which theperson is occupying.

Further, the origin module 2008 may determine upon which console or userinterface device 248 on the user interface of the vehicle 248 in whichthe gesture originates. With gestures that includes a tactile input on atouch screen or other electromechanical device, the origin module 2008can determine upon which console or device input the gesture originated.Gestures may also be given as other types of inputs that may not have aspecific device or console 248, but may be input by a device, such as amobile device, may be input onto a surface and then recognized by one ormore sensors, may be input either verbally or through other types ofphysical interaction, or may be input by other different means ormethods. Regardless, the origin module 2008 can determine where thegesture is made.

A focus module 2012, similar to an origin module 2008, can determine theplace upon which a user desires interaction. Unlike the origin module2008, the focus module 2012 can determine to which input device a userwishes to interact before that interaction occurs. For example, if auser begins to lean or move an arm towards a device console 248A, thefocus module 2012 may determine, in varying degrees of certainty, towhich console or other input device the user desires to interact.

As such, the focus module 2012, similar to the origin module 2008, canobtain sensor data from sensors, as described in conjunction with FIGS.2 and 6A through 7B. From the sensor data, the focus module 2012 candetermine a location within one or more zones 512 or areas 508 withinthe vehicle that a person occupies. When the user within the zone 512 orarea 508 desires to make an interaction, the person may begin to move ormake a physical indication of desiring to enter a gesture. The movementmay be viewed by the focus module 2012 and interpreted as having atarget for a gesture or input. The focus module may then determine wherethat target is and provide that information to a gesture recognitionmodule 2004.

A user customization module 2016 can change the way in which gesturesmay be received by the vehicle control system 204. A user customizationmodule 2016 can update or enact gesture preferences, as delineated by auser profile 1200, as described in conjunction with FIG. 12A. Thegesture preferences may be specific to an area 1216 or zone 1220. Thegestures 1232 can be different for each zone 512 or area 508, and may bedifferent if the user makes a gesture while occupying one zone 512 orarea 508 but makes the gesture in a different zone 512 or area 508.Further, a user customization module 2016 can also update audio and/orother inputs that the user may be able to make. The customizationinformation may be obtained from the user identification module 822,which interfaces with the profile data 252. The user customizationmodule 2016 may provide the customization information to the gesturerecognition module 2004.

A voice control module 2020 may receive and interpret any type of audioor voice inputs from the user. Thus, if the user makes a statement inthe vehicle interior, the statement may be received by a microphone, asdescribed in conjunction with FIGS. 6A and 6B. The received signalinformation may be sent to the voice control module 2020 through anaudio interface 874. The information may then be interpreted based onprofiles 1200, described in conjunction with FIG. 12A. If the voicecommand is determined to be a command to change a function of a vehicleor other interaction with the vehicle control system 204, the voicecommand or its subsequent interpretation may be sent to the gesturerecognition module 2004.

A verification module 2024 may be provided that can output averification of the gesture received. The gesture recognition module2004, after receiving information from one or more of the modules 2008through 2020, may determine the gesture desired by the user and sendthat information to the verification module 2024. The verificationmodule 2024 may then provide a name or other indication of what gesturewas received through an audio interface 874 to one or more speakers, asdescribed in conjunction with FIGS. 6A and 6B. There may be otherverifications possible, such as displays of information on a heads-updisplay or other console that may indicate which gesture was received.

In other situations, the verification module 2024 can give a preview ofthe gesture function. For example, if the user desires to turn on thecabin lights and states “turn on cabin lights,” the verification module2024 can turn on the cabin lights for a finite period of time, forexample 5 seconds, and then turn the cabin lights off.

The verification module 2024 may also be able to receive anyconfirmation from the user that the gesture as verified is the gesturedesired by the user. For example, if the verification module 2024 statesthat the user desired to turn on cabin lights, the verification module2024 can provide an audio verification that states “turn on cabinlights,” the user can reply by saying “yes,” “yes, please,” or someother type of audio or other gesture input. If the user does confirmthat the gesture is correct, the verification module 2024 may send thisinformation to the gesture recognition module 2004 to enact the functionor change desired by the user as confirmed by the verification module2024.

The gesture recognition module 2004 receives information from the originmodule 2008, focus module 2012, the user customization module 2016, thevehicle control module 2020, and/or the verification module 2024. Withinteractions with the modules 2008 through 2024, the recognition module2004 can interpret which gesture, as may be indicated within the userprofile data described in conjunction with FIG. 12A, the user desires toenact. Once the gesture is recognized and interpreted correctly,verified, and/or confirmed, the gesture recognition module 2004 can sendinformation to the vehicle control module 826 to enact whatever type ofgesture the user has provided.

An example of the vehicle control module 826 is shown in FIG. 21. Thevehicle control module 826 can be any hardware, software, combination ofhardware or software, or other electrical or code-based systems. Thevehicle control module 826 may be part of the user device andinteraction subsystem 817, as described in FIG. 8B. In other situations,for example, the vehicle control module 826 may be a separate functionembodied in a different system within the vehicle control system 204 ora separate function embodied in separate hardware and/or software. Inother examples, the vehicle control module 826 may be a software systemor application provided as a desktop plug-in 1024, as described inconjunction with FIG. 10. The vehicle control module 826 may have one ormore modules 2104 through 2136, as described hereinafter.

A function control module 2104 may receive information to control onemore functions of a vehicle. Based on information from a gesturerecognition module 834, the function control module 2104 may change oneor more of the vehicle functions or settings, as prescribed in the userprofile data described in conjunction with FIGS. 12A through 12D. Thevehicle functions controlled by the function control module 2104 may beas listed and described in conjunction with FIG. 22.

To communicate or control the vehicle functions, the function controlmodule 2104 may communicate and interact with one or more modules 2108through 2136. A sensor interface module 2108 may communicate with thesensor module 814, which can communicate with one or more sensors, asdescribed in conjunction with FIGS. 2 and 6A through 7B. The sensorinterface module 2108 can communicate, translate, or interpret anyinformation from the one or more sensors. The sensor information may beprovided to the function control module 2104 to change the function ofone or more of the functions of the vehicle. Further, the functioncontrol module 2104 may also adjust or change the interaction or tunethe one or more sensors based on activity or other information. Thus,the function control module 2104 may interact through the sensorinterface module 2108 to turn on or turn off sensors, change how thesensors function, or do other tasks.

The user customization module 2172 may communicate with the useridentification module 822. The user identification module 822 mayprovide profile data from profile database 252, which may be asdescribed in conjunction with FIGS. 12A through 12D. The user profileinformation 1200 may provide settings 1224, profile information 1238, orother information to the function control module 2104. Based on theprofile information, the function control module 2104 may change thefunction of one more vehicles settings, such as the display of one moreinterfaces 248 or other types of devices, displays, consoles, or othervehicle functions that provide information to or retrieve informationfrom a user.

A user interface (UI) module 2116 may communicate with a videoinput/output interface 864 to receive or output video information. Theuser interface module 2116 may also communicate with the functioncontrol module 2104 to change the function of one or more displays 248.Further, the UI module 2116 may also change a heads-up display or anytype of visual environment output that affects the user.

Similarly, the audio module 2120 can interact with the audioinput/output interface 874 to change the function of one or more audiooutputs/inputs. The audio module 2120 may also output any type ofcommunication from a function control module 2104 for provision to auser through a speaker 880 or other output.

The function control module 2104 can change or modify the one or morevehicle functions through vehicle function module 2124. The vehiclefunction module 2124 may communicate with one or more vehicle subsystems328, which may be as described in conjunction with FIG. 3. Further, thevehicle subsystems 328 may be as described in conjunction with FIG. 22.This vehicle function module 2124 is operable to communicate through oneor more communication pathways as described in conjunction with FIG. 4to change the function of one or more of the vehicle settings orsystems.

The function control module 2104 may also communicate through anenvironment module 2128 to an environmental control module 830. Throughthese communications, the function control module 2104 can change theenvironment for a user. The environment may include heating, airconditioning, lighting or other types of conditions which change how thevehicle functions for the user.

The function control module 2104 can also communicate through anavigation module 2132 to navigation subsystem 396, as described inconjunction with FIG. 8C. Navigation subsystems 336 may change how thevehicle provides route information or possibly how the vehicle steers orcontrols itself from an origination point to a destination point. Thefunction control module 2104 can provide or communicate with thenavigation module 2132 to change how the navigation subsystem 396functions.

The function control module 2104 may also communicate with the devicemodule 2136 to change the interaction parameters by communicating withthe device interaction module 818. In this way, the function controlmodule 2104 may change how a device may be accessed or operated within avehicle.

One or more different vehicle subsystems that may be controlled by afunction control module 2104 may be as described in conjunction and asshown in FIG. 22. Here, the different systems listed may be asunderstood in the art. For example, the vehicle systems may include oneor more of, but are not limited to, an ignition 2202, a transmissionfunction 2204, braking function 2206, an acceleration function 2208, oneor more doors 2210, a hood 2212, a trunk 2214, one or more windows 2116,a tire pressure system 2220, one or more locks 2222, a cruise controlfunction 2224, a parking system 2226, a steering function 2228, one ormore alarms 2230, a wiper system 2232, a headlight or exterior lightsystem 2234, an interior lighting system 2236, one or more mirrors 2238,a sunroof 2240, a convertible top 2242, or other systems that may beassociated with a vehicle. There may be more or fewer systems control bythe function control module as represented by ellipses 2298. Thesevehicle systems may be as understood in the art.

An ignition system 2202 may be any system that turns on or turns off thevehicle or starts or turns off the motor.

The transmission system 2204 may be any system that can change gears orchange the function of the transmission within the vehicle.

A braking system 2206 can be any system that causes the deceleration ofthe vehicle or engages brakes or an emergency brake for the vehicle.

An acceleration system 2208 can be any system that causes the vehicle toaccelerate or maintain a speed. Acceleration systems 2208 may include agas pedal, acceleration pedal, or any electronic system that may changethe speed of the vehicle.

The doors 2210, hood 2212, trunk 2214, and windows 2216 may be anysystem that can open a portal or part of a car. These systems canunlock, lock, open, or possibly close any of these different parts ofthe car.

A tire pressure system 2220 may be any system that monitors or possiblydeflates or inflates the tires or spare tire of a vehicle.

A lock system 2220 may be any system that can lock or unlock any of thedoors, trunk, hood, or other parts of the car.

A cruise control 2224 may be any system that controls the automateddriving system or systems that cause a cruise control to be engaged,disengaged, or changed.

A parking system 2226 can be any system that does automatic parking ormay help or provide information when parking a vehicle. The parkingsystem 2226 may include any brakes or other systems that may be engagedonce the car is parked.

A steering system 2228 may be any system that controls the steeringwheel of a car or any electronics or other electromechanical deviceswhich may be used instead of a steering wheel.

An alarm system 2230 may be any system that changes or controls thefunction of alarms. For example, the alarms can include a key left inthe ignition alarm, lights remain on, proximity warnings, blind spotwarnings, backing up warnings, or other types of alarms that may beprovided by the vehicle.

A wipers function 2232 may be any system that controls, turns on, turnsoff, or changes the operation of the windshield wipers, headlightwipers, rear windshield wiper, or other types of wipers that may be usedin a car. The wipers subsystem 2232 may also control any other devices,functions, or processes that can change or modify the function of anywindshield, window, or other type of transparent surface. For example,if the car uses a sonar or ultrasonic sound system to clear rain fromthe windshield, the wiper system 2232 may control that operation.

A headlights, exterior lights subsystem 2234 may be any system thatcontrols the headlights, tail lights, braking lights and reverse lights,or any type of lights that may exist on the exterior the vehicle. Thesystem 2234 may control both the on/off function and any type of highbeam or other change to the lights.

The interior lighting system 2236 may be any system that controls thecabin lights, foot-well lights, door puddle lights, or any type oflights that may exist on the interior of the vehicle. Interior lightingsystem 2236 may control the on/off function and any other change to theinterior lights including dimming or changing of the color of theinterior lights.

The mirror subsystem 2232 can include any type of system that controlsthe driver's side and passenger side rear view mirror, the rear viewmirror in the interior of the car, or any backup system that may provideinformation for looking to the rear of the vehicle. The mirror system2232 may adjust the positioning or functioning of these mirrorsincluding auto-dimming or any other type of process that changes how themirror operates.

The sunroof subsystem 2240 may control the function of the sunroof ormoon roof in the vehicle. The sunroof subsystem 2240 may open, close,tilt, change the covering, or complete other types of operations of thesunroof.

A convertible subsystem 2242 may control or operate the convertible top,which may be automated and include systems to open or close theconvertible top.

An embodiment of profile information 1238, which may be part of aprofile database 252, as described in conjunction with FIG. 12A throughFIG. 12D, may be as shown in FIG. 23A. The profile information 1238 mayhave one or more fields. There may be more or fewer fields than thoseshown in FIG. 23A, as represented by ellipses 2396. The fields withinthe profile information 1238 can include one or more of, but are notlimited to, an age field 2304, a driving experience field 2308, a loggedhours field 2312, an eyesight field 2316, a hearing field 2320, and/or acommon applications field 2324.

An age field 2304 may include an age or date of birth for a user. Theage may be provided in years, months, days, or other increments thatindicate how long the person has been alive.

The driving experience field 2308 can include the number of years, days,months, etc. that a user has been driving. In one example, the drivingexperience 2308 may be determined by a first driver's license issuedate. The driving experience may then be determined by the number ofyears, days, or other period of time between the first issue date of thedriver's license and the current date. Driving experience 2308 may alsobe provided by a user.

Driving experience 2308 can also include one or more situations in whicha user has been driving. For example, the driving experience 2308 mayindicate a positive indication of or number of minutes, hours, or otherperiods of time in which different types of conditions the driver hasencountered. For example, the driving conditions can include snowyconditions, rainy conditions, sleeting conditions, poor visibility,nighttime conditions, sunset conditions, or other types the conditionsencountered while driving. The driving experience field 2308 can provideindications of whether or not a driver may require assistance or havefunctions of vehicle change based on which environment the user iscurrently driving.

A logged hours field 2312 can include a number of hours a person hasbeen in this vehicle or all vehicles driven. The logged hours 2312 cangive an indication of the amount of driving experience. The logged hours2312 can also be broken into subcategories based on the drivingexperience data 2308. Thus, the driving experience data 2308 and loggedhours field 2312 may be linked by pointers or other information thatindicates a driving situation or driving experience/condition 2308 and anumber of logged hours for that driving experience in the logged hoursfield 2312. As such, between the driving experience 2308 and the loggedhours 2312 fields, an indication of the ability of the driver may bedetermined.

The eyesight 2316 and the hearing 2320 fields can give an indication ofa disability for user. The eyesight field 2316 may have an indicationthat the user wears glasses or contacts or may have, based on pastexperiences, indicated that the driver has trouble seeing in certainconditions. For example, if a user drives slower during a type ofdriving experience indicated in driving experience 2308, the vehiclecontrol system 204 may determine that the person's eyesight or hearingis poor and requires a change in the operation of the vehicle. Theeyesight field 2316 may also indicate other types of eyesight problemsbeyond just poor eyesight, such as, colorblindness, blind spots, poorperipheral vision, or other eyesight issues that may be deduced from thetype of driving done by the user. The hearing field 2320 may alsoindicate the ability for a user to hear both types of sounds, thedecibel level of sounds the user can hear or cannot hear, whether usersare able to hear during certain types of background noise, etc. Thus,the hearing field 2320, like the eyesight field 2316, providesinformation as to how the user functions in different types ofconditions.

A common applications field 2324 can include any type of softwareapplication on a device or used by a user in the car or on a device.These common applications 2324 also may have an indication of how oftenthe user uses an application or accesses that application while drivingin different conditions or how often the application is used as apassenger. A common applications field 2324 may include the applicationslisted hierarchically based on amount of usage. As such, the vehiclecontrol system 204 can access the applications more quickly for aparticular user based on frequency of use by that user.

An embodiment of gesture information 1232, as provided in the profiledatabase 252 and described in conjunction with FIGS. 12A through 12D,may be as shown in FIG. 23B. The information provided in the gestureinformation 1232 can provide information for a gesture and theassociated function that the gesture may invoke. The gesture information1232 can be standardized, as each person may use the same gesture toaffect the function, or may be user-created and may include theinformation provided from a user for certain functions. There may be asingle set of information for each type of gesture. The gestureinformation 1232 can provide any type of characteristics for the gesturethat may be as described in conjunction with FIGS. 11A through 11K. Thegesture information 1232 can include one or more of, but are not limitedto, a gesture name field 2328, a gesture characteristics field 2332, agesture results field 2336, an audio information field 2340, a previewfield 2344, etc. There may be more or fewer fields than those shown inFIG. 23B, as represented by ellipses 2398.

A gesture name field 2328 can include a name of the gesture. The gesturename 2328 may be, for example, a one word or several word description ofthe gesture. For example, the gesture name 2328 for turning the radiovolume up may include the words “radio,” “volume,” and “up.” The gesturename 2328 may be unique and provide both an indication to the database252 and to the user of what gesture is being requested or completed.

Gesture characteristics field 2332 can include any of thecharacteristics used to determine or identify one of the gestures inFIGS. 11A through 11K. The gesture characteristics 2332 information caninclude any type of vocal, visual, or tactile information received bythe vehicle control system 204. For example, a hand gesture in 3D spacemay include a configuration for a hand and a type or vector of movementthat is required by the vehicle control system 2004. Any of this gesturecharacteristics 2332 information may be stored in the gesturecharacteristics field 2332.

A gesture results field 2336 can include any information for thefunction or what type of process is required after receiving thegesture. Thus, if the user provides a gesture recognized by gesturecharacteristics 2332, the result 2336 should be some function performed.For example, if the user provides a gesture for turning the radio volumeup, the gesture results field 2338 can include any of the functions orprocesses required for turning up or increasing the volume of the radioand how much of the volume should be increased.

Audio information field 2340 may be any information provided back to theuser to verify the gesture and/or may be any data about a verbal commandthat may be associated with the gesture/function. The audio information2340 may also include other verification parameters that may be visual.For example, if the user desires to turn the volume up on the radio, theinformation 2340 can include the verification response, such as, “radiovolume up,” which may be spoken to the user through one or more speakers880. The audio information 2340 may also include any type ofconfirmation required by the user to enact the function of the gesture.For example, if the user is required to say “correct,” “yes,” or “enact”to cause the radio volume up gesture to be enacted, the audioinformation 2340 includes that response that as required by the user.The audio information field 2340 may also include any kind of visualresponse that may be provided to a heads up display or other display.This visual information may also include verification information, suchas, a button selection or other type of interaction that is required bythe user to verify the gesture.

A preview field 2344 includes any characteristics or informationrequired to preview the gesture results 2336 for a gesture. For example,if the user provides a radio volume up gesture, the preview field 2344may include a preview of turning a radio volume up for a specified andpredetermined amount of time. For example, the volume of the radio maygo up by 10% for 5 seconds. Thus, instead of having an audio or visualverification, the user can verify the command by the preview. If thepreview is not correct, the user can provide information or a responsefor denying or confirming the command. If confirmed, the gesture results2336 may mimic what was provided by the preview 2344.

Embodiments of different user interfaces that may be provided on display248 are shown in FIGS. 24A and 24B. A first user interface 2404A mayinclude three buttons for a first function 2408, a second function 2412,a third function 2416. The user interface 2404A can include differentfunction buttons or user interface devices 2408 through 2416, as shownin FIG. 24A for receiving input from a user. The buttons 2408 through2416 or user interface devices may be selectable by a user on a touchscreen device or other console. The function buttons 2408 through 2416can each have a different function associated the button 2408 through2416. Each of the buttons 2408 through 2416 may have a different color,shape, location, or configuration visually for the user. For example,function buttons 2408 and 2412 are square, large, and at the top of thescreen 2404A. A function button 2416 may be in the middle of the screen,may be rectangular, and may be larger than the first two functionbuttons 2408 and 2412. Each of the different configurations may bechanged based on user data or interactions with the user.

A second user interface 2404B (which may provide an interface for thesame application or process) is shown in FIG. 24B. Here, the buttons2408 through 2432 may have changed based on different settings andinteractions with the user. For example, function buttons 2408 through2416 are now located at the top of the screen, are square, and are muchsmaller than shown in 2404A. Further, more function buttons 2420, 2424,2428, and 2432 have been added to the user interface 2404B. For example,function button 2424 is not provided on the user interface of 2404A.Further, function buttons 2428 and 2432 are round and located the bottomof the user interface.

Both user interfaces 2404A and 2404B may be associated with a commonapplication that may be executed by the vehicle control system 204.Thus, the common application may have different user interfaces, whichmay be changed based on device settings 1224, profile information 1238,or an interaction parameter, as determined by the vehicle control system2004. Further, one user interface 2404A may be provided to a first user,while a second user interface 2404B may be provided to a second user.Further, these different user interfaces 2404A, 2404B may be provided tothe different people while those people are in the vehicle operating thesame console 248. Thus, depending on which user is using the console 248at which time, the user interface 2404 may change. It should be notedthat any type of visual, audio, tactile, configuration of a userinterface, or other interaction configurations may be changed by thevehicle control system.

An embodiment of the method 2500 for receiving a gesture or other inputmay be as shown in FIG. 25. A general order for the steps of the method2500 is shown in FIG. 25. Generally, the method 2500 starts with a startoperation 2504 and ends with an end operation 2532. The method 2500 caninclude more or fewer steps or can arrange the order of the stepsdifferently than those shown in FIG. 25. The method 2500 can be executedas a set of computer-executable instructions executed by a computersystem and encoded or stored on a computer readable medium. Hereinafter,the method 2500 shall be explained with reference to the systems,components, modules, software, data structures, user interfaces, etc.described in conjunction with FIGS. 1-24.

A receive step 1716, which may be as described in conjunction with FIG.17, may receive a gesture. The gesture may be provided to a gesturerecognition module 2004. The gesture recognition module 2004 may alsoreceive a voice input or other type of input into a display 248. Thegesture recognition module 2004 may then identify the gesture, in step1720, which may be as described in conjunction with FIG. 17. Once thegesture is identified, the gesture information may be provided from thedatabase, as described in conjunction with FIG. 23B, to a verificationmodule 2024.

The verification module 2024 may retrieve the gesture information, instep 2508. The information may be retrieved from information sent by thegesture recognition module 2004 or by information that is accessedthrough the profile database 252, as described in conjunction with FIG.23B. The gesture information can include any kind of characteristics orinformation 2332-2344 required by the verification module 2024 to send averification to the user.

The verification module 2024 may then retrieve the audio or visualinformation from field 2340 or the preview or other type of informationfrom field 2344 to send the verification, in step 2512. Here, theverification module 2024 may provide an audio verification output to anaudio input/output interface 874 to send to one more speakers 880. Thisaudio output can include the name of the gesture 2328 or otherinformation that may be provided in the data field 2340. For example, ifthe user provided a gesture that is recognized as turning all theinterior lights on, the verification module 2024 may provide an audiooutput that states “all interior lights on” through the speaker 880. Theverification module 2024 may access the media controller 348 to signalthe speech synthesis module 820 to provide a voice-like audio outputthat states “all interior lights on” through the audio input/outputinterface 874 to the speakers 880. In this way, a synthesized humanvoice may state what gesture was recognized by the gesture recognitionmodule 2004.

In other examples, the verification module 2024 can provide a visualindication of the gesture as recognized. For example, a verificationmessage may be displayed on a display 248 on the head unit or one of theconsoles 248. For example, a message “all interior lights on,” in text,may be displayed on one of the user interfaces 248. In other situations,a symbolic character, such as a flashing light bulb, may be presentedthat indicates the gesture requested was that all interior lights beturned on. The visual indication may be provided on one more the visualuser interfaces 248 and may include some type of confirmation button oruser interface device that may be selected to confirm that verifiedgesture is associated with the correct function desired by the user. Instill other examples, another user interface device may be provided thatstates that the verified gesture is incorrect.

In other examples, the verification module 2024 may provide a preview,as described in preview field 2344. A preview of all the interior lightson may require the verification module 2024 to send a signal to thefunction control module 2104 to control, through the vehicle functionmodule 2024, a vehicle subsystem 328. The vehicle function controlmodule 2104 can send a “lights on” signal to the interior lights system2236 to turn on the interior lights for some definite and predeterminedamount of time. For example, the interior lights system 2236 may turn onthe interior lights for a period of 5 seconds. The preview may then bepresented with the either an audio or visual confirmation request. Forexample, one more user interface devices may be presented on one or moreuser interfaces 248 that may be selected by the user to either confirmor to deny that the preview is associated with the correct function. Anaudio indication may also be provided asking whether the preview wascorrect.

A user may then provide either a confirmation or a denial to theverification module 2024 of whether the verified gesture is correct. Theverification module 2024 can determine if a confirmation is received, instep 2516. Here, the verification module 2024 may receive a signalthrough the audio input/output interface 874, video input/outputinterface 864, a video controller 840, an audio controller 844, othersystem that controls the input side of the devices 248. Thus, a modulecan send a signal back to the verification module 2024 to indicatewhether a user selectable device, confirming the verification, wasselected. Further, the audio input/output interface 874 may receive asignal from a microphone 886 that can be sent to the verification module2024, And in still other examples, one or more sensors, as described inconjunction with FIG. 6A through 7B, may determine if a confirmationgesture is received by the user. Regardless, some type of user actionmay be perceived and sent to the verification module 2024. If the userhas confirmed the gesture as recognized, the method 2500 proceeds YES tostep 2528. However, if no confirmation or a denial is received, themethod 2500 may proceed NO to step 2520.

In step 2520, the verification module 2024 can determine whether tocomplete the function associated with the gesture. For example, if theuser provides no confirmation, but a confirmation is assumed if noconfirmation occurs after a predetermined period of time, for example 5seconds, the gesture may still be completed. As such, the user mayacquiesce to a function without interaction. Thus, no confirmation or nointeraction from user may be a confirmation. If the gesture is to becompleted, the method 2500 proceeds YES to step 2528. However, if thegesture is not to be completed, the method 2500 may proceed NO to step2524.

In some situations, the verification module 2024 may determine to resendthe verification message, in step 2524. For example, if no confirmationis received and the gesture is not to be completed unless a confirmationis indicated, the verification module 2024 may require at least sometype of confirmation. As such, if the verification is to be resent, themethod 2500 proceeds YES back to step 2512 where the verification module2024 may resend the verification message either visually, audibly,tactilely, by vibration, or through another type of signal. Theverification module 2024 may then wait for a period of time to determineif the confirmation is sent. The verification module 2024 may resend theverification message some predetermined number of times beforedetermining that the gesture is denied or is not confirmed. If theverification is not to be resent, the method 2500 proceeds NO back toreceive step 1716, where the gesture may be resent, and the user may tryand input the gesture again and have the gesture re-recognized becausethe verified gesture was either wrong or inadvertent.

In step 2528, the verification module 2024 confirms that the gesture wasrecognized accurately and sends that indication back to the gesturerecognition module 2004. The gesture recognition module 2004 may thensend a signal to the function control module 2104 to complete a functionassociated with the gesture. The function control module 2104 may thenenact any type of function associated with that gesture. The signal sentfrom the gesture recognition module 2004 can provide either the gestureor the function information. If the function control module 2104receives the gesture information, the function control module 2104 maylook up the function associated with that gesture in a database, asdescribed in conjunction with FIG. 23B. As such, the function controlmodule 2104 may retrieve the gesture results information 2336 and enactthe function required by the gesture.

An embodiment of a method 2600 for changing the function of a vehiclebased on user characteristics is as shown in FIG. 26. A general orderfor the steps of the method 2600 is shown in FIG. 26. Generally, themethod 2600 starts with a start operation 2604 and ends with an endoperation 2628. The method 2600 can include more or fewer steps or canarrange the order of the steps differently than those shown in FIG. 26.The method 2600 can be executed as a set of computer-executableinstructions executed by a computer system and encoded or stored on acomputer readable medium. Hereinafter, the method 2600 shall beexplained with reference to the systems, components, modules, software,data structures, user interfaces, etc. described in conjunction withFIGS. 1-25.

The user identification module 822 can retrieve user characteristics,settings, profile information, etc., in step 2608. The retrieval ofsettings from a user profile 1200 may be as described in FIG. 14 throughFIG. 19. Thus, FIG. 26 may be a further addendum to customization of thevehicle based on user profile 1200. Here, the user may be recognized asdescribed previously in FIGS. 14 through 19. The user identificationmodule 822 may then retrieve user characteristics, in step 2608. Theuser identification module 822 may retrieve the information as describedin conjunction with FIG. 23A. This information may then be sent to theuser customization module 2172.

The user customization module 2172 may then access thecharacteristic(s), as described in conjunction with FIG. 23A, todetermine if any of the characteristics may impact the function of thevehicle, in step 2612. Here, the user customization module 2112 may useone more rules to determine if any of the characteristics are over orunder a benchmark or within an area of concern. The rules may includequantitative or qualitative assessments of the differentcharacteristics. For example, if the user's age 2304 is below apredetermined age, for example, age 20, the user customization module2172 may determine that that characteristic requires some type ofcustomization or change to a function of the vehicle.

The user customization module 2172, if determining that thecharacteristic does impact a function, may then retrieve any type of thesettings 1224 that may be required or needed to address thatcharacteristic. The settings information may then be sent to a functioncontrol module 2104. Thus, if the characteristics do impact a functionof the vehicle, the method 2600 proceeds YES to step 2616. However, ifno characteristic does affect a function of a vehicle, the method 2600proceeds NO to end step 2628.

The function control module 2104 or the user customization module 2172may then determine if there was an override, in step 2616. An overridemay be a user-provided or an automatic override that eliminates theadjustment of any of the vehicle functions based on usercharacteristics. The override, if set, may require the function controlmodule 2104 or the user customization module 2172 to ignore or not adoptany of the settings provided in field 1224. If there an override set orenacted, method 2600 proceeds YES to end step 2628. However, if nooverride is provided, method 2600 proceeds NO to step 2620.

The function control module 2104 may then determine which functions areaffected by the characteristics, in step 2620. Here, the functioncontrol module 2104 may retrieve settings 1224 that are associated withthe changes based on the characteristics. In other situations, thefunction control module 2104 may access a standardized set of changesrequired based on a characteristic. For example, if a person's eyesightis poor, the standardized set of functions that are changed are toincrease the size, vibrancy, and accessibility of any of the controlsprovided on a user interface 248. Other changes may be associated withother different characteristics.

The function control module 2104 then proceeds to change thosefunctions, in step 2624. Here, the function control module 2104 may sendone more commands or control signals through one more modules 2116through 2136 to change the functions of the vehicle. The differentfunctions may then be modified to control user interfaces, vehiclefunctions, or other types of processes, functions, or means that modifyhow the vehicle interacts with the user or how the vehicle operates. Thechanges may include gesture preferences, vehicles settings, infotainmentsystem controls, climate control settings, access and manipulation ofthe dashboard, console functions or layouts, or one or more vehiclessubsystems.

An example includes changing access to vehicle features or functionsbased on the user's age 2204, driving experience 2308, logged hours2312, or other characteristic. For example, a user may have an age 2304that is under some benchmark (the user is 16 and under the benchmark ageof 20) that causes one or more vehicle functions to be changed. Forexample, the function control module 2104 may receive furtherinformation from the sensor data sensor module 814 that three people arewithin the car. The laws of the state may require the function controlmodule 2104 to prohibit a teenage driver from having more than onepassenger within the car. As such, the ignition system 2202 may bedisengaged and not allow the user to turn on the car based on the numberof passengers and their age characteristic 2304.

In another example, one or more distractions may be eliminated based ona user profile or other condition currently being encountered by thevehicle. As such, the function control module 2104 may receiveinformation from sensor module 814 and compare that to characteristics,as described in conjunction with FIG. 23A. For example, the user mayhave a limited amount of driving experience indicated in fields 2308 or2312 and is driving in a dangerous condition or at high speed, thefunction control module 2104 may then limit the amount of information inone or more vehicle user interfaces to provide for a less distractingenvironment. For example, the head unit or dashboard may be changed topresent only information which is critical, for example, speed warningsor other types of critical information. As such, the user has to viewthe limited information only for a short amount of time, compared to anormal dashboard display, to see what is critical to their currentdriving situation.

Further, if a distraction may be inevitable when the convertible top isopen (such as when it is raining), the convertible systems 2242 may belimited such that the user's environment is more contained and outsidedistractions are not possible. Further, if there's a type of situationwhich may cause the user to be distracted if the convertible top isopen, the convertible systems 2242 may be disabled. Further, the radiooperations may be changed such that channels may be restricted or theamount of volume provided is lowered. Thus, if the user is lessexperienced, the user's amount of radio interaction may be changed suchthat the user maintains a lower volume of the radio and has fewerchannels to select.

An Internet access may be restricted for drivers under a certain age orunder a certain amount of experience. As such, if the vehicle isoperable to access the Internet, the access may be restricted to onemore passengers within the vehicle and may not be accessible to thedriver. Further, applications may be restricted based on age or otherinformation. For example, if a game is presented but is a game only forpeople who are 17 years old or older, a passenger in the rear of thevehicle that is under such an age may be restricted from playing thatgame. Further, the applications store may be limited to people withaccess to purchase applications. As such, passengers in the back thatare not old enough to access or do not have the correct identity toaccess the applications may restricted from any applications store. Assuch, distractions may be changed for the driver and for any passengerbased on information in the profile 1238.

These examples also connote that the profile permissions 1238 can alsochange how vehicle functions are provided to passengers and drivers. Thefunction vehicle control module 2104 can also change how a transmissionsystem 2204 is used based on information in the database 1238. Forexample, if there's a law against high speed acceleration, or the userhas less driving experience, the transmission may restrict higher gearsor may change the ability to speed or accelerate the car based on gearchanges. As such, the car's function when driving may be changed basedon characteristics.

The function control module 2104 may also interact with the navigationsystem 336 through the navigation module 2132. Thus, based oncharacteristics provided in information shown in FIG. 23A, the type ofnavigation or route information provided may change. For example, ayounger driver may only be provided with routes that are safer, havelower traffic, and prevent interaction with heavy traffic scenarios. Assuch, the user is less likely to get in situations where their drivingexperience 2308, logged hours 2312, or age 2308 have not prepared them.For an older driver that may have poor eyesight, as indicated in field2316, or poor hearing is indicated in field 2320, the routes may beprovided that have better lighting or other conditions for that user.Further, the user may be provided with routes that limit the exposure toheavy traffic, pedestrian walkways, wildlife, or other situations thatrequire a quicker reaction time that may be determined in the drivingexperience section 2308. Further, based on the time and the drivingexperience 2308, the maps may be included with live traffic data whennecessary. Further, the mapping utility can also suggest that a userwait for some period of time before starting the vehicle or beginningtheir route based on the current traffic conditions associated therewithin comparison to their experience or logged hours. Further, the user maybe prevented from continuing a route or starting a route based on thetraffic conditions or other information if the characteristics indicatethat that user may not be able to handle the current conditions, such asbad weather or heavy traffic.

A method 2700 for receiving a gesture may be as shown in FIG. 27. Ageneral order for the steps of the method 2700 is shown in FIG. 27.Generally, the method 2700 starts with a start operation 2704 and endswith an end operation 2724. The method 2700 can include more or fewersteps or can arrange the order of the steps differently than those shownin FIG. 27. The method 2700 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method2700 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-26.

The gesture may be received, in step 716. The reception of a gesture maybe as described in conjunction with FIG. 17. The origin module 2008 canreceive information from one or more sensors through a sensor module814. The sensors may be described in conjunction with FIGS. 6A through7B. The sensor module 814 can provide the information to the originmodule 2008 to determine a location of a gesture, in step 2708. Todetermine the location, the origin module 2008 can determine in whichzone 512, area 508, or location within a zone 512 of a vehicle interiorthe gesture is received. Thus, if one or more sensors associated withspecific zone 512A identify that gesture as being provided within zone A512A, the origin module 2008 can determine that the location of thegesture is in zone A 512A. However, other sensors may determine that thegesture is received in zone B 512 B, or in other zones 512C through 512Nof the vehicle.

The origin module 2008 may then determine if the location of thereceived gesture is different from the user providing the gesture, instep 2712. Thus, the origin module 2008 may receive information from theuser identification module 822 or sensor module 814 to determine alocation of one more passengers within the zones 512A through 512N. Forexample, the origin module 2008 may determine there's only a singleperson in the vehicle and is seated within zone A 512A. The gesture maybe received in zone B 512B, which is different from the location of userthat made the gesture. In other examples, the origin module 2008 may useother information to determine that the user providing the gesture is ina different location within the vehicle. For example, one or moresensors may provide information to sensor module 814 that indicates anoccupant may be reaching out of one zone into another zone to providethe gesture. For example, as a passenger in zone D 512D reaches into thefront passenger area 508A and provides a gesture in 512B, the sensormodule 814 may provide information that the person's body or armstretches out of zone D and into zone B. Thus, the origin module 2008may user pattern recognition to identify a gesture when the userreaches. The origin module 2008 may interpret any of this information todetermine that the user may be in different location than the locationof the gesture. Based on the location of the gesture and location theuser, the origin module 2008 may send information to the gesturerecognition module 2004 of the origin and location of the gesture.

The gesture recognition module 2004 may then determine the origin of thegesture based on the information provided by the origin module 2008. Thegesture recognition module 2004 can use the origin of the gesture tolook up gesture information from the profile 1200, as described inconjunction with FIGS. 12A-12D.

The gesture recognition module 2004 may then identify a gesture, in step2720. The identification of the gesture, in step 2720, may be similar tothat as described in step 1720 of FIG. 17. However, in this situation,the gesture recognition module 2004 may use the origin of the gestureand location of the user as factors in determining which gesture wasreceived. For example, a user may make a gesture within zone A 512A thatmay mean a first function is desired. However, if that same gesture ismade by the user in zone B 512B, that gesture may require a differentfunction. Thus, although the user is located in one zone, for example,zone A 512A, gestures the user makes may have different meaning if madein a separate zone 512 from which the user is occupying. For example, auser in zone D 512D may make a first gesture to change the content of adisplay provided in zone D or in area 2 508B. However, if that samegesture is made in zone B 512B, from that occupant in zone D 512D, thefunction associated with the gesture is different.

In this way, the number of gestures, available to control functions, isexpanded. Further, gestures within another zone 512 may be prohibitedbased on the location of the user and where the gesture was made. Forexample, a user in zone D 512D may not be able to provide any gesturesin zone A 512A, as those gestures may be detrimental or hazardous. Assuch, occupants in zone D 512D may be prohibited or blocked from makinggestures in area 508A or zone A 512A. The gesture recognition module2004 can determine the location of the gesture, but also all thelocation of the user to determine the origin of that gesture todetermine if the gesture should be recognized at all.

An embodiment of a method 2800 for changing the functions of the vehiclebased on the focus of a user is shown in FIG. 28. A general order forthe steps of the method 2800 is shown in FIG. 28. Generally, the method2800 starts with a start operation 2804 and ends with an end operation2820. The method 2800 can include more or fewer steps or can arrange theorder of the steps differently than those shown in FIG. 28. The method2800 can be executed as a set of computer-executable instructionsexecuted by a computer system and encoded or stored on a computerreadable medium. Hereinafter, the method 2800 shall be explained withreference to the systems, components, modules, software, datastructures, user interfaces, etc. described in conjunction with FIGS.1-27.

A gesture control module 834 may receive a gesture initiation, in step2806. A gesture initiation may be the beginning of a type of gesture butmay not be a completion of the gesture. A gesture initiation may bepreceded by one more other gestures or may be preceded by a physicalmovement or interaction of the user with the vehicle. For example, if auser in zone A 512A reaches for a console in the center of a head unit,the gesture recognition module 2004 may determine that a gesture isbeing initiated.

The focus module 2012 can receive sensor information from sensors, asdescribed in conjunction with FIGS. 6A and 7B that are sent to a sensormodule 814. The focus module 2012 can determine that a gesture is beinginitiated. Pattern recognition or other information may be used todetermine that the gesture is being initiated on an interface 248 or inthree dimensional space, as described with gestures in FIGS. 11A through11K.

Upon determining that a gesture is being initiated, the focus module2012 can then determine a target or focus of the gesture for the user,in step 2808. For example, if the user is reaching for a user interface2408, the focus module 2012 may determine by a vector or a physicalpositioning of an arm, finger, or other physical part of the user 2016to which display 248 the user is reaching or with which the user isattempting to interact. In other situations, the user may reach into athree dimensional space used for three dimensional gestures or may reachfor or into some other type of input area. The focus module 2012 maydetermine by the movement or interaction of the user (which may bedetermined from past interactions with this user) to which system orinterface the user is focusing. The information of the focus may beprovided from the focus module 2012 to the gesture recognition module2004.

The gesture recognition module 2004 may then send information about userinterface 248 or other system the user is focusing upon to the functioncontrol module 2104. The function control module 2104 may then determineone more user characteristics, in step 2812. The user characteristicsmay be described in profile information 1200, as described in FIGS. 12Athrough 12D. Further, the user characteristics may also include any kindof current environmental information (e.g., the current drivingconditions, cabin conditions, etc.) associated with the user. Forexample, the information can include which zone 512 the user currentlyoccupies, what device the user is currently using, the interaction theuser is currently making within the vehicle 104. These usercharacteristics may then be studied by the function control module 2104to determine if one more settings may be changed.

In step 2816, the function control module 2104 may control one or moreof the settings of a system based on the focus. The changes to thesettings may be made before the user interacts with the system allowingthe user less distraction or easier access to certain functions of asystem based on the gesture initiation. For example, the functioncontrol module 2104 may change the configuration or display of the userinterfaces, as described in FIGS. 24A and 24B, based on the usercharacteristics and a gesture focus. For example, if a driver in zone A512A is initiating a gesture to a center console 2408, the userinterface 2404A may be changed as shown in FIG. 24A. As such, fewerbuttons are provided and those buttons are easily selectable or providedbecause the driver has less time to be distracted or less time to taketheir focus off of the road.

Thus, the focus module 2012 can determine that the interaction with thisinterface 2404 is being initiated. The function control module 2104based on this determination can then change the interface from thatshown in FIG. 24B to that shown in 24A to allow the user to focus on theimportant functions they may wish to select. Other changes may be madeto vehicle systems or controls settings based on what the focus of theuser is before the user provides the initial gesture.

An embodiment of the method 2900 for preventing access by the user toone more user interfaces based on the current conditions of the userwithin the vehicle 104 is shown in FIG. 29. A general order for thesteps of the method 2900 is shown in FIG. 29. Generally, the method 2900starts with a start operation 2904 and ends with an end operation 2932.The method 2900 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 29. The method 2900can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 2900 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-28.

A media controller 348 or other system may provide content on one ormore user interfaces 248, in step 2908. For example, a passenger in zoneB 512B may be viewing a video on a center console 248, as provided by amedia controller 348. Information about the video may be provided, fromthe media controller 348, to a UI module 2116 of the vehicle controlmodule 826. Then, the information may then be provided by a functioncontrol module 2104 to a user customization module 2172. The usercustomization module 2172 may then access profile data 252 or sensordata provided from sensor module 814.

With the provided information, the user customization module 2172 candetermine if there is a driver or passenger who should not view and/orhear the current content provided in the user interface 248, in step2912. For example, the driver that is operating the vehicle in zone A512A may be prohibited from viewing the video content provided tooccupants in zone B 512B, based on state law or simply for safetyreasons. As such, the user customization module 2172 may determine thatthe driver should not see or hear the content being provided to thepassenger in zone B 512B. In other situations, a passenger in zone E512E may be viewing video or the other information which is meant foradults. As such, if a child is determined to be in zone C 512C, thevideo or content should be prohibited from being seen by the child inzone C 512C. As such, if it is determined that a user should not see,hear, or be able to interact with the content provided, the method 2900proceeds YES to step 2916. However, if it is determined that the usercan see, hear, or interact with the content, the method 2900 proceeds NOback to step 2908 where that content is provided.

The user customization module 2172 may then access sensor informationfrom sensor module 814. From that information, the user customizationmodule 2172 can determine the location of the user that should notinteract or view the content, in step 2916. This location informationmay then be sent to the function control module 2104.

The function control module 2104 may then change at least a portion ofthe user interface or other device or system to prevent viewing of orinteraction with the content by the prohibited user, in step 2920. Forexample, the function control module 2104 may instruct the mediacontroller 348 to change the video output through the video I/Ointerface 864 to the screen 248. The change may include blacking out oneor more portions of the screen to prevent the prohibited user fromseeing the video. The function control module 2104 may determine fromsensor information provided by the sensor module 814 every time the usermoves their eyes to look to the video. If the user does attempt to viewthe video, the video will be blacked out for all occupants. As such, theuser will not be provided content, and therefore, does not attempt toview the video.

In other situations, an electromechanical pivot may be used so that thescreen is pivoted away from the prohibited user and will not allow thatoccupant to see the video screen at an angle that allows them to viewthe video. In other situations, one or more types of electromechanicalor electrical systems may be used to polarize the signal or change theviewing parameters of the screen such that the prohibited user is unableto view the video when looking at the screen but the visual signal isstill sent to the other user(s). As such, the change in the screen, instep 2920, prevents the user who is prohibited from viewing the contentfrom actually viewing the information on the screen or viewing thescreen at all.

The function control module 2104 may also receive a signal from usercustomization module 2172 as to whether the prohibited user is alsoprohibited from listening to any of the audio associated with thecontent. Thus, the user customization module 2172 can also determine ifaudio is not to be provided, in step 2924. The profile data or the typeof content being provided may indicate whether the audio should beprovided. For example, if a movie is being viewed, the soundtrack to themovie can be distracting for a driver in zone A 512A. As such, the audiomay not be desired in that zone 512A. As such, the user customizationmodule 2172 may send a signal to the function control module 2104 to notprovide the audio in zone 512A. If the user customization module 2172determines that no audio is to be provided, the method 2900 proceeds YESto step 2928. However, if the user customization module 2172 determinesthe audio is not distracting or can be provided to all occupants, themethod 2900 proceeds NO back to step 2908 to provide the content.

In step 2928, the function control module 2104 can change the audioconditions for the prohibited user. For example, the function controlmodule 2104 can send a signal or information to the audio I/O interface874 to control one more speakers 880. The speakers may change thedirection of sound to limit sound that may leak into the zone of theprohibited user. Thus, the speakers 880 may be changed electrically orphysically to direct sound only to a certain area 508B or 508A or into aspecific zone 512A through 512N. In other situations, noise cancelingtechnology may be used to project a noise canceling signal from speakers880 into the prohibited user's zone 512. As such, the noise cancelingsignal actually creates a cone or an area of silence around the personwithin that zone. Regardless, the function control module 2104 cancontrol systems to change how the user receives audio within that zone512 or area 508.

In other situations, the passengers in the other zones may be requiredto use headphones or other systems that prevent audio from beingprojected across the speakers. There are many ways to control the videoand audio content within a car; these systems are controlled by thefunction control module 2104 to prohibit one or more users within thevehicle from viewing content if that content is unfit or unsuitable forthe current situation.

An embodiment of a method 3000 for receiving voice commands in thevehicle environment is shown in FIG. 30. A general order for the stepsof the method 3000 is shown in FIG. 30. Generally, the method 3000starts with a start operation 3004 and ends with an end operation 3040.The method 3000 can include more or fewer steps or can arrange the orderof the steps differently than those shown in FIG. 30. The method 3000can be executed as a set of computer-executable instructions executed bya computer system and encoded or stored on a computer readable medium.Hereinafter, the method 3000 shall be explained with reference to thesystems, components, modules, software, data structures, userinterfaces, etc. described in conjunction with FIGS. 1-29.

A voice control module 2020 may interface with a sensor module 814 toreceive voice commands, in step 3008. The audio signal is received, by amicrophone 886, and provided through the audio I/O interface 874 to thevoice control module 2020. The voice command can then be interpreted bythe voice control module 2020.

A user identification module 822 can identify a user within the vehicle,in step 3012. The identification of the user may be as described inconjunction with FIGS. 13 through 19. Further, the user identificationmodule 822 can receive sensor information from the sensor module 814 todetermine an area 508 in which the person or user occupies, in step3016, and determine the zone 512 which the user occupies, in step 3020.The detection of which area 508 and zone 512 the user is in may be asdescribed in conjunction with FIGS. 13 through 19.

Based on the identity of the user, the user identification module 822may then retrieve characteristics or settings in a user profile 1200 andprofile data 252, in step 3024.

The characteristics and settings of the profile 1200 may be as describedin conjunction with FIGS. 12A and 23A. This information may be retrievedas described in conjunction with FIGS. 13 through 19. The settings orprofile data may be as described in conjunction with the FIGS. 12A, 23A,and 23B, and may indicate one or more different audio commands that areassociated with the user.

Each user may have a customizable set of audio settings that the usercan provide and store, as described in conjunction FIGS. 13 through 19.Further, there may be a standard set of audio commands that any user mayuse within the vehicle. Each audio command may be associated with anarea 508 and/or a zone 512. Thus, a first command used in zone A 512Amay cause of a first function to be controlled or process to beexecuted, while that same audio command used in zone E 512E may have adifferent function or process executed. As such, based on the area 508or zone 512, upon which the user occupies, the audio commands may causedifferent processes or functions to be executed.

One audio command that may be completed is a search. Thus, the user maysearch for a function or command audibly. The voice control module 2020can determine if a search is being conducted, in step 3028. A search maybe one type of command that can be used anywhere within the vehicle.Thus, the voice control module 2020 may search for gesture or voiceinformation in field 2340 to determine if a search command is beingexecuted. If a search command is not being executed, the method proceedsNO to step 3028. However, if a search is being conducted, the method3000 proceeds YES to step 3032 where the voice control module 2012provides the search information to the gesture recognition module 2004.The gesture recognition module 2004 may then instruct the mediacontroller 348 or the vehicle control module 826 to provide a searchfunction, in step 3032. Information about the search function may beincluded and then used to identify another function.

The vehicle control module 826 may then perform the function based onthe verbal communication(s), in step 3032. Thus, if the voice command isidentified, the information is sent to the function control module 2104.The function control module 2104 may perform the function based on thereceived information, in step 3032. In this way, the voice command canbe used for the vehicle systems, as described in conjunction with FIG.22.

An embodiment 3100 of configuring user interactions based on usercharacteristics and user history is shown in FIG. 31. A general orderfor the steps of the method 3100 is shown in FIG. 31. Generally, themethod 3100 starts with a start operation 3104 and ends with an endoperation 3132. The method 3100 can include more or fewer steps or canarrange the order of the steps differently than those shown in FIG. 31.The method 3100 can be executed as a set of computer-executableinstructions executed by a computer system and encoded or stored on acomputer readable medium. Hereinafter, the method 3100 shall beexplained with reference to the systems, components, modules, software,data structures, user interfaces, etc. described in conjunction withFIGS. 1-30.

The user interaction module 822 may identify a user, in step 3108. Here,the user action module 822 may identify the user as explained in FIGS.13 through 19. The user identification module 822 may then retrievecharacteristics of the user and/or the user history from profile data252, in step 3112. The user identification module 822 may retrieve thisinformation as described in conjunction with FIGS. 13 through 19. Thecharacteristics may be the characteristics as described in conjunctionwith FIGS. 12A through 12D or the information as described inconjunction with FIG. 23A. Further, the history or information of theuser may also include common applications accessed or used by the userduring other periods of operating a vehicle or riding within thevehicle, as provided in the common applications field 2324. Thus, thecommon applications field 2324 can provide a history of access to whatapplications, for how long, and in what situations. This information maybe provided by the user in identification module 8222 to the vehiclecontrol module 826.

The user customization module 8172 may receive the information anddetermine if a change to an interaction interface associated with theuser may be required, in step 3116. Thus, the characteristics such asage, driving experience, other information described in conjunction withFIG. 23A, the common applications, and the current situation of thevehicle, as indicated by sensor module 814, may be input into the usercustomization module 2172. The user customization module 2172 candetermine if a change may be necessary to a user interface 248 or otheruser interaction within the system. If a change is determined to beneeded, the method 3100 proceeds YES to step 3120. However, if no changeis needed, the method 3100 may proceed NO to end step 3132.

In step 3120, the user customization module 2172 may provide theinformation about the suggested changes to the function control module2104. The function control module may then instruct the verificationmodule 2024 or the gesture recognition module 2004 to suggest thechange. The verification module 2024 may suggest a change by making anaudio, visual, or tactile suggestion or by making a preview for theuser.

The verification module 2024 may then receive or detect if the useraccepts the changes, in step 3124. It should be noted that it is notnecessary to suggest that the changes be made, the changes may be madeautomatically without input from the user—made automatically without theuser being able to accept or deny the changes. If the user does acceptthe changes in step 3124, the method proceeds YES to step 3128. However,if the user does not accept the changes, the method 3100 proceeds NO tostep 3132. The verification module 2024 can receive the acceptance ofthe changes and provide that confirmation through the gesturerecognition module 2004 to the function control module 2104. Here, thefunction control module 2104 may then send commands through the userinterface module 2116 to change the function of one or more userinterfaces 2408 or other systems controlled by the video I/O interface864, audio I/O interface 874, etc. The configuration of the UI may becompleted in step 3128.

As an example, the user customization module 2172 may determine theuser's age, gender, type of applications used, type of email program,what other activity the user partakes in while inside the vehicle. Theuser customization module 2172 may also determine how the user typicallydigests information. For example, if the user has poor eyesight or theirage may indicate difficulties reading information on the screen if thescreen is too crowded. The information may be presented in an alteredconfiguration. For example, the senior citizen with poor eyesightrequires to access a GPS application (which is the only application thisuser ever accesses). The GPS application may be presented in the userinterface with larger icons that are easily selectable for the driver.For example, as shown in FIGS. 24A and 24B, GPS application may includefunction buttons F1 through F3 shown in user interface 2404A. However,in a standard user interface shown in FIG. 2424B, other function buttonsfor other different applications may be presented. However, thoseapplication buttons may be eliminated in a simplified screen shown inFIG. 24A with only the GPS user interface selectable devices 2408through 2416 shown in the interface 2404. The buttons may be changed tomake them more easily selectable by the user.

In another example, the passenger or driver may be a teenager. Theteenager may have several applications they wish to access, such asFacebook and Twitter. However, if the teenage driver is attempting toaccess the user interface with these types of applications whiledriving, those application buttons may also be eliminated, preventingdistractions from the teenage driver. Thus, the user interface shown inFIG. 24B may include a Facebook button 2420 and/or a Twitter button 2424that are eliminated when user interface 2404A is presented to the user.Depending on the common applications used by the user, their age, andother characteristics, the user interface 2404 may be changed to betterprovide an easily interactive user interface for the user based on thecharacteristics.

The exemplary systems and methods of this disclosure have been describedin relation to configurable vehicle consoles and associated devices.However, to avoid unnecessarily obscuring the present disclosure, thepreceding description omits a number of known structures and devices.This omission is not to be construed as a limitation of the scopes ofthe claims. Specific details are set forth to provide an understandingof the present disclosure. It should however be appreciated that thepresent disclosure may be practiced in a variety of ways beyond thespecific detail set forth herein.

Furthermore, while the exemplary aspects, embodiments, options, and/orconfigurations illustrated herein show the various components of thesystem collocated, certain components of the system can be locatedremotely, at distant portions of a distributed network, such as a LANand/or the Internet, or within a dedicated system. Thus, it should beappreciated, that the components of the system can be combined in to oneor more devices, such as a Personal Computer (PC), laptop, netbook,smart phone, Personal Digital Assistant (PDA), tablet, etc., orcollocated on a particular node of a distributed network, such as ananalog and/or digital telecommunications network, a packet-switchnetwork, or a circuit-switched network. It will be appreciated from thepreceding description, and for reasons of computational efficiency, thatthe components of the system can be arranged at any location within adistributed network of components without affecting the operation of thesystem. For example, the various components can be located in a switchsuch as a PBX and media server, gateway, in one or more communicationsdevices, at one or more users' premises, or some combination thereof.Similarly, one or more functional portions of the system could bedistributed between a telecommunications device(s) and an associatedcomputing device.

Furthermore, it should be appreciated that the various links connectingthe elements can be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying and/or communicating data to and from the connected elements.These wired or wireless links can also be secure links and may becapable of communicating encrypted information. Transmission media usedas links, for example, can be any suitable carrier for electricalsignals, including coaxial cables, copper wire and fiber optics, and maytake the form of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Also, while the flowcharts have been discussed and illustrated inrelation to a particular sequence of events, it should be appreciatedthat changes, additions, and omissions to this sequence can occurwithout materially affecting the operation of the disclosed embodiments,configuration, and aspects.

A number of variations and modifications of the disclosure can be used.It would be possible to provide for some features of the disclosurewithout providing others.

It should be appreciated that the various processing modules (e.g.,processors, vehicle systems, vehicle subsystems, modules, etc.), forexample, can perform, monitor, and/or control critical and non-criticaltasks, functions, and operations, such as interaction with and/ormonitoring and/or control of critical and non-critical on board sensorsand vehicle operations (e.g., engine, transmission, throttle, brakepower assist/brake lock-up, electronic suspension, traction andstability control, parallel parking assistance, occupant protectionsystems, power steering assistance, self-diagnostics, event datarecorders, steer-by-wire and/or brake-by-wire operations,vehicle-to-vehicle interactions, vehicle-to-infrastructure interactions,partial and/or full automation, telematics, navigation/SPS, multimediasystems, audio systems, rear seat entertainment systems, game consoles,tuners (SDR), heads-up display, night vision, lane departure warning,adaptive cruise control, adaptive headlights, collision warning, blindspot sensors, park/reverse assistance, tire pressure monitoring, trafficsignal recognition, vehicle tracking (e.g., LoJack™),dashboard/instrument cluster, lights, seats, climate control, voicerecognition, remote keyless entry, security alarm systems, andwiper/window control). Processing modules can be enclosed in an advancedEMI-shielded enclosure containing multiple expansion modules. Processingmodules can have a “black box” or flight data recorder technology,containing an event (or driving history) recorder (containingoperational information collected from vehicle on board sensors andprovided by nearby or roadside signal transmitters), a crash survivablememory unit, an integrated controller and circuitry board, and networkinterfaces.

Critical system controller(s) can control, monitor, and/or operatecritical systems. Critical systems may include one or more of (dependingon the particular vehicle) monitoring, controlling, operating the ECU,TCU, door settings, window settings, blind spot monitor, monitoring,controlling, operating the safety equipment (e.g., airbag deploymentcontrol unit, collision sensor, nearby object sensing system, seat beltcontrol unit, sensors for setting the seat belt, etc.), monitoringand/or controlling certain critical sensors such as the power sourcecontroller and energy output sensor, engine temperature, oil pressuresensing, hydraulic pressure sensors, sensors for headlight and otherlights (e.g., emergency light, brake light, parking light, fog light,interior or passenger compartment light, and/or tail light state (on oroff)), vehicle control system sensors, wireless network sensor (e.g.,Wi-Fi and/or Bluetooth sensors, etc.), cellular data sensor, and/orsteering/torque sensor, controlling the operation of the engine (e.g.,ignition, etc.), head light control unit, power steering, display panel,switch state control unit, power control unit, and/or brake controlunit, and/or issuing alerts to a user and/or remote monitoring entity ofpotential problems with a vehicle operation.

Non-critical system controller(s) can control, monitor, and/or operatenon-critical systems. Non-critical systems may include one or more of(depending on the particular vehicle) monitoring, controlling, operatinga non-critical system, emissions control, seating system controller andsensor, infotainment/entertainment system, monitoring certainnon-critical sensors such as ambient (outdoor) weather readings (e.g.,temperature, precipitation, wind speed, and the like), odometer readingsensor, trip mileage reading sensor, road condition sensors (e.g., wet,icy, etc.), radar transmitter/receiver output, brake wear sensor, oxygensensor, ambient lighting sensor, vision system sensor, ranging sensor,parking sensor, heating, venting, and air conditioning (HVAC) system andsensor, water sensor, air-fuel ratio meter, hall effect sensor,microphone, radio frequency (RF) sensor, and/or infrared (IR) sensor.

It is an aspect of the present disclosure that one or more of thenon-critical components and/or systems provided herein may becomecritical components and/or systems, and/or vice versa, depending on acontext associated with the vehicle.

Optionally, the systems and methods of this disclosure can beimplemented in conjunction with a special purpose computer, a programmedmicroprocessor or microcontroller and peripheral integrated circuitelement(s), an ASIC or other integrated circuit, a digital signalprocessor, a hard-wired electronic or logic circuit such as discreteelement circuit, a programmable logic device or gate array such as PLD,PLA, FPGA, PAL, special purpose computer, any comparable means, or thelike. In general, any device(s) or means capable of implementing themethodology illustrated herein can be used to implement the variousaspects of this disclosure. Exemplary hardware that can be used for thedisclosed embodiments, configurations and aspects includes computers,handheld devices, telephones (e.g., cellular, Internet enabled, digital,analog, hybrids, and others), and other hardware known in the art. Someof these devices include processors (e.g., a single or multiplemicroprocessors), memory, nonvolatile storage, input devices, and outputdevices. Furthermore, alternative software implementations including,but not limited to, distributed processing or component/objectdistributed processing, parallel processing, or virtual machineprocessing can also be constructed to implement the methods describedherein.

In yet another embodiment, the disclosed methods may be readilyimplemented in conjunction with software using object or object-orientedsoftware development environments that provide portable source code thatcan be used on a variety of computer or workstation platforms.Alternatively, the disclosed system may be implemented partially orfully in hardware using standard logic circuits or VLSI design. Whethersoftware or hardware is used to implement the systems in accordance withthis disclosure is dependent on the speed and/or efficiency requirementsof the system, the particular function, and the particular software orhardware systems or microprocessor or microcomputer systems beingutilized.

In yet another embodiment, the disclosed methods may be partiallyimplemented in software that can be stored on a storage medium, executedon programmed general-purpose computer with the cooperation of acontroller and memory, a special purpose computer, a microprocessor, orthe like. In these instances, the systems and methods of this disclosurecan be implemented as program embedded on personal computer such as anapplet, JAVA® or CGI script, as a resource residing on a server orcomputer workstation, as a routine embedded in a dedicated measurementsystem, system component, or the like. The system can also beimplemented by physically incorporating the system and/or method into asoftware and/or hardware system.

Although the present disclosure describes components and functionsimplemented in the aspects, embodiments, and/or configurations withreference to particular standards and protocols, the aspects,embodiments, and/or configurations are not limited to such standards andprotocols. Other similar standards and protocols not mentioned hereinare in existence and are considered to be included in the presentdisclosure. Moreover, the standards and protocols mentioned herein andother similar standards and protocols not mentioned herein areperiodically superseded by faster or more effective equivalents havingessentially the same functions. Such replacement standards and protocolshaving the same functions are considered equivalents included in thepresent disclosure.

The present disclosure, in various aspects, embodiments, and/orconfigurations, includes components, methods, processes, systems and/orapparatus substantially as depicted and described herein, includingvarious aspects, embodiments, configurations embodiments,subcombinations, and/or subsets thereof. Those of skill in the art willunderstand how to make and use the disclosed aspects, embodiments,and/or configurations after understanding the present disclosure. Thepresent disclosure, in various aspects, embodiments, and/orconfigurations, includes providing devices and processes in the absenceof items not depicted and/or described herein or in various aspects,embodiments, and/or configurations hereof, including in the absence ofsuch items as may have been used in previous devices or processes, e.g.,for improving performance, achieving ease and\or reducing cost ofimplementation.

The foregoing discussion has been presented for purposes of illustrationand description. The foregoing is not intended to limit the disclosureto the form or forms disclosed herein. In the foregoing DetailedDescription for example, various features of the disclosure are groupedtogether in one or more aspects, embodiments, and/or configurations forthe purpose of streamlining the disclosure. The features of the aspects,embodiments, and/or configurations of the disclosure may be combined inalternate aspects, embodiments, and/or configurations other than thosediscussed above. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive aspects lie in less than all features of a singleforegoing disclosed aspect, embodiment, and/or configuration. Thus, thefollowing claims are hereby incorporated into this Detailed Description,with each claim standing on its own as a separate preferred embodimentof the disclosure.

Moreover, though the description has included description of one or moreaspects, embodiments, and/or configurations and certain variations andmodifications, other variations, combinations, and modifications arewithin the scope of the disclosure, e.g., as may be within the skill andknowledge of those in the art, after understanding the presentdisclosure. It is intended to obtain rights which include alternativeaspects, embodiments, and/or configurations to the extent permitted,including alternate, interchangeable and/or equivalent structures,functions, ranges or steps to those claimed, whether or not suchalternate, interchangeable and/or equivalent structures, functions,ranges or steps are disclosed herein, and without intending to publiclydedicate any patentable subject matter.

This application is also related to PCT Patent Application Nos.PCT/US14/______ filed on Apr. 15, 2014, entitled, “Building ProfilesAssociated with Vehicle Users” (Attorney Docket No. 6583-543-PCT);PCT/US14/______, filed on Apr. 15, 2014, entitled “Access andPortability of User Profiles Stored as Templates” (Attorney Docket No.6583-544-PCT); PCT/US14/______, filed on Apr. 15, 2014, entitled “UserInterface and Virtual Personality Presentation Based on User Profile”(Attorney Docket No. 6583-547-PCT); PCT/US14/______, filed on Apr. 15,2014, entitled “Creating Targeted Advertising Profiles Based on UserBehavior” (Attorney Docket No. 6583-549-PCT); PCT/US14/______, filed onApr. 15, 2014, entitled “Behavior Modification via Altered Map RoutesBased on User Profile Information” (Attorney Docket No. 6583-550-PCT);PCT/US14/______, filed on Apr. 15, 2014, entitled “VehicleLocation-Based Home Automation Triggers” (Attorney Docket No.6583-556-PCT); PCT/US14/______, filed on Apr. 15, 2014, entitled“Vehicle Initiated Communications with Third Parties via VirtualPersonalities” (Attorney Docket No. 6583-559-PCT); PCT/US14/______,filed on Apr. 15, 2014, entitled “Vehicle Intruder Alert Detection andIndication” (Attorney Docket No. 6583-562-PCT); PCT/US14/______, filedon Apr. 15, 2014, entitled “Driver Facts Behavior Information StorageSystem” (Attorney Docket No. 6583-565-PCT); PCT/US14/______, filed onApr. 15, 2014, entitled “Synchronization Between Vehicle and User DeviceCalendar” (Attorney Docket No. 6583-567-PCT); PCT/US14/______, filed onApr. 15, 2014, entitled “User Gesture Control of Vehicle Features”(Attorney Docket No. 6583-569-PCT); PCT/US14/______, filed on Apr. 15,2014, entitled “Central Network for the Automated Control of VehicularTraffic” (Attorney Docket No. 6583-574-PCT); and PCT/US14/______, filedon Apr. 15, 2014, entitled “Vehicle-Based Multimode Discovery” (AttorneyDocket No. 6583-585-PCT). The entire disclosures of the applicationslisted above are hereby incorporated by reference, in their entirety,for all that they teach and for all purposes.

Examples of the processors as described herein may include, but are notlimited to, at least one of Qualcomm® Snapdragon® 800 and 801, Qualcomm®Snapdragon® 610 and 615 with 4G LTE Integration and 64-bit computing,Apple® A7 processor with 64-bit architecture, Apple® M7 motioncoprocessors, Samsung® Exynos® series, the Intel® Core™ family ofprocessors, the Intel® Xeon® family of processors, the Intel® Atom™family of processors, the Intel Itanium® family of processors, Intel®Core® i5-4670K and i7-4770K 22 nm Haswell, Intel® Core® i5-3570K 22 nmIvy Bridge, the AMD® FX™ family of processors, AMD® FX-4300, FX-6300,and FX-8350 32 nm Vishera, AMD® Kaveri processors, Texas Instruments®Jacinto C6000™ automotive infotainment processors, Texas Instruments®OMAP™ automotive-grade mobile processors, ARMED Cortex™-M processors,ARM® Cortex-A and ARM926EJ-S™ processors, other industry-equivalentprocessors, and may perform computational functions using any known orfuture-developed standard, instruction set, libraries, and/orarchitecture.

What is claimed is:
 1. A method for controlling a user interface in aconveyance, comprising: a vehicle control system, including a processor,providing content on the user interface; the vehicle control systemdetermining if a user within the conveyance should be prohibited fromviewing the content; the vehicle control system determining a locationof the prohibited user; and the vehicle control system modifying adisplay of the content to prevent viewing by the prohibited user.
 2. Themethod of claim 1, wherein the content is a movie.
 3. The method ofclaim 1, wherein the prohibited user is a driver.
 4. The method of claim1, wherein the prohibited user is another passenger.
 5. The method ofclaim 4, wherein the other passenger is identified as a child.
 6. Themethod of claim 1, wherein at least a portion of the user interface isblacked out.
 7. The method of claim 6, wherein the at least a portion ofthe user interface is blacked out when the prohibited user looks at theuser interface.
 8. The method of claim 7, wherein the user interface ispivoted away from the prohibited user.
 9. The method of claim 8, furthercomprising: the vehicle control system determining if the prohibiteduser should receive audio associated with the content; and if theprohibited user should not receive audio associated with the content,changing an audio signal to prevent listening by the prohibited user.10. The method of claim 9, wherein a noise cancelling signal is sent toa zone associated with the prohibited user.
 11. A conveyance comprising:a processor operable to execute one or more modules, the modulescomprising: a media controller operable to: provide content on the userinterface; modify a display of the content to prevent viewing by a user;a user customization module operable to: determine if the user withinthe conveyance should be prohibited from viewing the content; anddetermine a location of the prohibited user.
 12. The conveyance of claim11, wherein the content is a movie.
 13. The conveyance of claim 12,wherein the prohibited user is one of a driver, another passenger, or achild passenger.
 14. The conveyance of claim 13, wherein the display ismodified by one of at least a portion of the user interface is blackedout when the prohibited user looks at the user interface or the displayis pivoted away from the prohibited user.
 15. The conveyance of claim14, wherein the user customization module is further operable to:determine if the prohibited user should receive audio associated withthe content; and if the prohibited user should not receive audioassociated with the content, change an audio signal to prevent listeningby the prohibited user, wherein a noise cancelling signal is sent to azone associated with the prohibited user.
 16. A non-transitory computerreadable medium stored on a storage medium and having instructions thatwhen executed by a processor cause the processor to perform a method,the instructions comprising: instructions to provide content on the userinterface; instructions to determine if a user within the conveyanceshould be prohibited from viewing the content; and instructions todetermine a location of the prohibited user; instructions to modify adisplay of the content to prevent viewing by the prohibited user. 17.The computer readable medium of claim 16, wherein the content is amovie.
 18. The computer readable medium of claim 17, wherein theprohibited user is one of a driver, another passenger, or a childpassenger.
 19. The computer readable medium of claim 18, wherein thedisplay is modified by one of at least a portion of the user interfaceis blacked out when the prohibited user looks at the user interface orthe display is pivoted away from the prohibited user.
 20. The computerreadable medium of claim 19, further comprising: instructions todetermine if the prohibited user should receive audio associated withthe content; and if the prohibited user should not receive audioassociated with the content, instructions to change an audio signal toprevent listening by the prohibited user, wherein a noise cancellingsignal is sent to a zone associated with the prohibited user.